Add CI for automated Python package release

[juice500ml]

• What kind of change does this PR introduce? (Language addition, bug fix, feature, docs update, ...)
  Add CI for automated Python package release

• What is the current behavior? (You can also link to an open issue here)
  We have to manually release the package.

• What is the new behavior (if this is a feature change)?
  We want to automatically release the package.

• Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
  No.

[juice500ml]

Closing & reopening PR for triggering CI

[juice500ml]

• https://python-semantic-release.readthedocs.io/en/stable/configuration/automatic-releases/github-actions.html#gh-actions-examples
• https://guicommits.com/semantic-release-to-automate-versioning-and-publishing-to-pypi-with-github-actions/
• https://www.conventionalcommits.org/en/v1.0.0/

[dmort27]

I looked these over, and they seem sensible. Aside from the commit conventions, what do we need to do in order to make this work?

[juice500ml]

I'm currently working on updating pyproject.toml + Github Actions at #232.
In the meantime, it'll be nice if you could:

• briefly guide me through your usual process of pypi releases
• do this for Github actions: https://docs.pypi.org/trusted-publishers/adding-a-publisher/

We can go through together during our tmr's meeting