Setup Github action to publish releases

[Flamefire]

I'd recommend to setup a Github action (CI) to publish a release to PyPI automatically.

Goal: More frequent releases

Motivation: The current master contains many valuable enhancements (the latest being the CInstrumenter but there have been others before I started) which are not in any release hence it is harder than it should to get a "good" version

Solution: On each pushed tag a new release on PyPI is automatically created. Hence this process becomes much easier: Change version in __version__.py, git tag <tag> and git push origin <tag>

https://packaging.python.org/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/ describes how to do this. I could create the workflow file (~5min work) if the tokens are registered in the project. Just need to know if the shown 2nd workflow uploading every commit to testpypi is wanted.
I'd also add a check that the tag and the version.py match. Question is what should be done if they don't: Don't upload the release (need to retag)? Change it then upload (github tag contains different files to PyPI)?

[AndreasGocht]

As there are a lot of people have acces to this repo I do have a frew security concerns. Lets please have a shor call about this.

[AndreasGocht]

Btw: https://github.com/score-p/scorep_binding_python_dummy would need that as well.

[AndreasGocht]

We still need to have the call. But I do like the Idee better from day to day.