Coordinate with IREE stable release process and implement any missing process/automation

[stellaraccident]

The last couple of times, I've been doing the monthly release manually. This time I wrote down the steps I took. This should be automated in some fashion.

Notes for releasing Turbine and IREE

(Note: This is still being done manually but most of it is up for being automated. Just recording notes for now)

Release dependent IREE version

Typically since Turbine development is pinned to IREE pre-release candidates, we need to push the IREE version we depend on to
PyPI. This is typically uncontroversial and Turbine is often the motivator. Coordinate on the IREE discord server.

When ready, verify that the IREE version in requirements.py needs to be pushed and push it with build_tools/python_deploy/pypi_deploy.sh in the IREE repo.

Turbine Release Steps

Ensure you are on main and clean.

cd SHARK-Turbine
git switch main
git fetch
git reset --hard origin/main
git status

Create a release issue

Create an issue like: #280

Set version

Edit version_info.json at the cut revision and set the version. Generally this involves removing the dev* suffix that
was added as the last step of the previous cycle.

Create a local commit with the version change

git add version_info.json
git commit -m "Pin version to 0.9.3.

Progress on #280
"

Tag the release

git tag v0.9.3
git push origin v0.9.3

Build wheel and push

cd SHARK-Turbine
pip wheel .
twine upload --verbose shark_turbine-0.9.3-py3-none-any.whl
rm -f *.whl

Prepare for the next release.

cd SHARK-Turbine
git fetch
git reset --hard origin/main

Increase version number in version_info.py (including the .dev1 suffix).

Commit:

git add version_info.py
git commit -m "Advance to 0.9.4.dev1 after prior release.

Fixes #280.
"
git push origin