Add Github Release to releasing workflow

[joshuadavidthomas]

I would think a simple job step at the end of the release.yml workflow would be fine.

[joshuadavidthomas]

You know, my typical workflow for releasing things is:

• Open a PR with all the meta changes that are needed for a new release (e.g., CHANGELOG, bumping the version where it needs, making sure docs are up to date)
• Merge PR when everything looks good and CI passes
• Creating a new release via gh release create v0.0.0 --generate-notes
• Having that GH release kick off a release workflow that builds and publishes everything

Went a bit in a different direction on this project, primarily because the CI workflow generated by maturin was setup this way. I wonder if I shouldn't just use the workflow I'm comfortable with?

Only issue is if the CI workflow changes in maturin for any reason, it will overwrite any customizations I have. Though, not a huge deal, we can just deal with the diff and keep what we want. I think I'd like to be able to customize the release workflow anyway.

[joshuadavidthomas]

Even though I kinda like the intermediate PR to catch things just before release, it would be nice to just push a tag via bumpver and have that kick off the whole thing. Though I would like to somehow check the things that need to be updated are, before this. Not sure if bumpver has pre and post checks (pretty sure they do), but if not there could be a nox session that could handle this too.

[joshuadavidthomas]

Things that should be run before release:

• just cog -- to make sure all cog uses in docs have been run and are the most up to date
• just docs build -- copies the README over to the docs and processes it for use in mkdocs
• change unreleased heading in changelog and add link at bottom
• make sure uvlock is updated
• bump versions across project -- handled by bumpver

[joshuadavidthomas]

LOL, i must have gone through this before because there are .bin/bumpver_{post,pre}.sh files. I've since started using Python scripts with the uv inline deps in other projects, would be nice to move on from bash to this.

[joshuadavidthomas]

Closed in #103.

For now we'll run the nox release session, which prepares everything and pushes a tag, which kicks off the release workflow. Then create a GH release after the fact by hand, but I'd like to explore automating this too eventually.