Automate release process

Current process:
1. Update history, documentation, version
2. Tag, push tags
3. Update wheels.yml for new Starforge version, PR, test wheel/sdist, merge
4. `twine upload -s starforge--*`
5. `ssh jenkins@mjolnir0 ./sfvenv/bin/pip install --upgrade starforge` <-- Jenkins could just do this on every build
6. Update image configs to install the new Starforge version
7. Rebuild _all_ of the Docker/QEMU images =/
8. Push the Docker images to Docker Hub.

Start by reading wheels.yml and the image configs referenced in the release steps, then trace the Jenkins build and Docker/QEMU image rebuild process. Done would mean the listed release steps are automated end to end, including publishing the wheel/sdist and Docker images, but the issue does not specify an implementation or acceptance checks.

Written by the indexing model from the issue text.