ci/docs: add release workflow (publish to pypi) and a RELEASE.md file

[consideRatio]

PR Summary

• The github secret PYPI_PASSWORD is added already, based on a deployment token for our PyPI bot account now with maintainer permissions for the associated PyPI project.
• Added a copy/pasted/tweaked RELEASE.md based on this workflow of relying on the github CI system to do upload to PyPI.

Related

It would be nice to retroactively add tags to the commits associated with the previous releases and push those before merging this to avoid triggering workflows that would try publish to PyPI. If that is done later, they won't override any PyPI release though because the upload command looks like this: twine upload --skip-existing dist/*

• 35

[yuvipanda]

Is there something I should do to move this forward? :D

[consideRatio]

Review merge :)

[yuvipanda]

Done :)