Resolve "Automated build"

Closes #37 (closed) Packaging, uploading the package and creating a gitlab release is now triggered by adding a new tag (not a release!). The release notes of the new tag MUST be empty.
Packaging and uploading should work. For now it points to the testpypi instance. After testing it from creating a test-tag, we can point the upload URL to the production instance of PyPI.

.gitlab-ci.yml

@@ -67,7 +67,6 @@ pages:
     - public
   rules:
   - if: "$CI_COMMIT_REF_NAME == $CI_DEFAULT_BRANCH"
-  - when: manual
 
 sast:
   before_script:
@@ -95,14 +94,12 @@ include:
 
 build_and_upload:
   stage: package
-  needs: []
   script:
     - pip install build twine
     - python3 -m build
     - TWINE_PASSWORD=${CI_PYPI_TOKEN} TWINE_USERNAME=__token__ python3 -m twine upload --repository testpypi dist/* 
   rules:
-  - if: "$CI_COMMIT_REF_NAME == $CI_DEFAULT_BRANCH"
-  - when: manual
+  - if: $CI_COMMIT_TAG
 
 release_job:
   stage: release

[Hock, Martin]

We should not push all commit tags, put only those that fit a version tag like "vX.Y" or "vX.Y.Z"