Minor Version Release workflow: rc0 tag wrongly placed

[masci]

Describe the bug
The workflow minor_version_release has the following responsibilities:

1. Create the release branch for minor versions, e.g. 2.2.x
2. Bump the version number in VERSION.txt in main
3. Tag main with a special tag with the format <next.release-rc0>, e.g. 2.3.0-rc0

At the moment the workflow tags the main branch at the same commit where we branch off the minor release. This confuses reno that will generate wrong release notes from the version branch.

Expected behavior
The -rc0 tag should be applied to the subsequent commit after we branch out the release branch. For example

<main> (TAG: 2.3.0-rc0)
c3
 |
c2 --- c4 - c5 <2.2.x>
 |
c1

Additional context
Since the workflow creates a PR to update VERSION.txt, we should find a way to tag the main branch AFTER that PR is merged.

[shadeMe]

Unfortunately, the fix isn't trivial as it'll involve splitting the workflow into another and trigger in on specific PRs. Furthermore, it'll only be a band-aid over the complicated release process - time would be better served to simplify/refactor the latter (in the direction of the workflow we have for core integrations).

Moving it back to the backlog.