Improve release process by implementing release-please

[thrbnhrtmnn]

Description / User story

As discussed on 06.06.2024 we should critically question, if we really need a main environment. We could also just tag the last commit to develop, when we want to release something.

With this issue we want to improve the current release process to be able to release more easily in the future.

This issue includes:

• Creating a release action
• Documenting the release process in the docs folder (check if this should be added to existing files, before creating a new one)

We could use "release-please" as a bot (built by google) to do the release. DEVEN is also using this (check out documentation-skeleton doc here and telemetry doc here). release-please uses the standard gitflow process, which we are also currently using.

We should discuss first, what we really want in the end. Do we need automatic change logs? Do we want to use conventional commits? When this is clear we can define what we do next.

Requirements / Prerequisites

• none

Acceptance Criteria

• Release action has been created and tested and allows us to effortlessly make new releases
• Release process has been documented (see DEPLOYMENT.md) and documentation has been shared with the team

Additional information

• Documentation of the current branching strategybranch
• Documentation of our rules for commits
• The release process should be documented in the DEPLOYMENT.md
• To test release-please, we should fork the repository, implement release-please and see how a release would look with it.

Code of Conduct

• I agree to follow this project's Code of Conduct

[thrbnhrtmnn]

We decided today to move "switchting from develop to main" and "changing location of Token JSON" out of this scope.