GeezerVison

I'm working on fixing the broken notarization for macos. But in order to do that I want to make sure that:

1. we don't need to publish a new release in order to validate our changes
2. we need to gate publishing to maven and gradle until we know all of the desktop (linux,macos, windows) actually are good

How the release flow works now

1. Push a processing-<build>-<version> tag
2. create-draft makes the draft release with auto-generated notes
3. This will trigger all of the platform build steps, and upon success it will publish maven and gradle
4. When everything's green, publish-release reaches the release environment and pauses, showing a "Review pending" prompt on the run
5. Edit the draft's release notes
6. Approve the deployment in the Actions