GitHub action for publishing packages fails

[mrmorrandir]

There is a github action that publishes packages on every merge.

1. This action should only be triggered if you really want to have a new release. (BestPractice?)
2. The action has the same problem as the build validation for pull-requests: the integration tests fail because of missing RabbitMQ.

[mrmorrandir]

@kammeph do you have an idea or a best practice for this package release process? Using tags with special names to trigger the release etc? Let me know 😉

[mrmorrandir]

In the corresponding branch I configured the trigger now to "manually" and "push on releases/**" - do you think this is a good practice @kammeph?