Release Environment - Automatically create a new environment when tagging a new version

Currently, creating a new release environment is the last step in the monthly release issue. When we automate it, it means less tasks for RMs. Furthermore, it also automatically creates a new environment when we want to do a patch release of a out-of-policy version.

Exit Criteria

• A new release environment is created when a new stable branch is created via ChatOps /chatops run release tag XX)
  • It means a file environments/<environment-name/environment.yaml is committed, and deployment is done to deploy the new environment to the release cluster
• Create follow-up issue to drop the release_environment feature flag: #20086

Out of Scope

• Test the environment creation during 16.10. It is done in Test adding a new release environment automatic... (#20095 - closed)