Updated release workflow

[effigies]

With the extensive CI tests and nipreps dependency tree, the release process has grown a bit cumbersome. I've tried the following for the 23.1.x series to try to streamline things a little bit, and I'm recording it here. Comments welcome.

Minor release (YY.N.0)

• Start maint/YY.N.x branch. At this point, changes for the next minor release can start being merged into master.
• Change @master pins to the latest releases of nipreps dependencies
• pip-compile --extra=telemetry --resolver=backtracking --upgrade
• Update changelog and Zenodo ordering
• Push to upstream and create PR for review

After review

• Tag directly on maint/YY.N.x branch with git tag -a YY.N.0 and push upstream
• After successful deployment, merge the tag into master, e.g.

  $ git checkout master
  $ git fetch upstream
  $ git reset --hard upstream/master
  $ git merge YY.N.0 --no-commit
  $ git checkout upstream/master pyproject.toml  # Do not pin nipreps dependencies in master
  $ git commit
  $ git push upstream master

Merging the tag into master will close the release PR as merged.

Bug fix release (YY.N.n)

• Merge and/or cherry-pick approved fixes into maint/YY.N.x branch
• Update any nipreps dependencies in pyproject.toml
• pip-compile --extra=telemetry --resolver=backtracking (no --upgrade)
• Update changelog and zenodo ordering
• Push to upstream to start final CI

After successful CI build

• Tag directly on maint/YY.N.x branch with git tag -a YY.N.n and push upstream
• After successful deployment, merge the tag into master using the same process as above