Document release workflow

[SRichner]

https://www.electron.build/configuration/publish.html#recommended-github-releases-workflow

same as recommended,

• update version in package
• push to main
• create draft release
• tag prefix version with v

[AlexanderLill]

Thanks for the issue!

Just adding a bit more detail as I am "fresh" to GitHub workflows and might know the least about it :)

According to the official electron recommendations[1]

• update version in src/electron/package.json (what about package-lock.json?)
• push commit to main (this happens before creating the draft release?)
• create draft release in GitHub ("Draft a new release"-button on [2])
• tag prefix version with v${version}, e.g. v0.0.20 (git-tag and push to main? Or is this the content of the version-field that needs to be specified when creating a new release according to the previous step?)
• Project builds and automatically puts build assets into the created draft release (is that what indeed happens?)

[1] https://www.electron.build/configuration/publish.html#recommended-github-releases-workflow
[2] https://github.com/HASEL-UZH/PersonalAnalytics/releases

[casaout]

I've created a release docu: https://github.com/HASEL-UZH/PersonalAnalytics/blob/dev/documentation/RESEARCH.md#releasing-personalanalytics

@AlexanderLill Feel free to check/adapt/extend it if you have suggestions for improvement!