Fix automated release / tagging

[joshjohanning]

See: #47 (comment)

For some odd reason the release pipeline was using an older commit as a baseline and this resulted in another 3.0.0 release ergo the pipeline failed with tag 'v3.0.0' already exists. I created the release manual for now, but the same happened earlier before as well see #43 (comment) @gr2m do you have any idea what is causing this?

Given this is happening since #39 it must be related to this change. Is there another way to address #23?

cc @stefanbuck @gr2m

[evverx]

Looking at systemd/systemd#25900 (comment) I wonder if the code was force-pushed and the history was overwritten at some point?

[gr2m]

Tags or commits currently cannot be used directly because they lack the dist/ folder, e.g. https://github.com/stefanbuck/github-issue-parser/tree/v3.2.0

I suggest we copy the setup of https://github.com/actions/create-github-app-token, where the dist/ folder is updated automatically as part of the release directly in the default branch. Repository rules now allow branch protections to be circumvented for actors, so we can register a single purpose GitHub App for this task, in order to keep branch protections in tact as they are

[gr2m]

See also #74

[jamacku]

Also #82