Deploy to release environment on all merges to stable branches

What does this MR do and why?

Deploy to release environment on all merges to stable branches

Change the rule to run the stage release-environments on all merges to a stable branch, not only the ones that match .setup-test-env-patterns.

This way, a deployment to a release environment is also triggered when a new release is created. The release creates a special commit that changes the VERSION file, so it doesn't match .setup-test-env-patterns.

Ref: gitlab-com/gl-infra/delivery#20163 (closed)

Examples about the current status before this change

• start-release-environments-pipeline is not added:
  • when tagging v16.10.0-ee https://gitlab.com/gitlab-org/gitlab/-/pipelines/1220742239
  • when releasing v16.11.0-rc42-ee https://gitlab.com/gitlab-org/gitlab/-/pipelines/1254947767
• start-release-environments-pipeline is added:
  • when merging a MR to 16-10-stable-ee branch: https://gitlab.com/gitlab-org/gitlab/-/pipelines/1226252042

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before	After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.