Backport of 'Exclude release environments from QA live envs'

What does this MR do and why?

Describe in detail what merge request is being backported and why

Exclude release environments from QA live envs

See merge request !198778 (merged)

Testing

I tested the QA image built by this MR's pipeline against https://gitlab.18-2-stable-security-get.env.release.gitlab.net and it succeeded.

• Job log: https://gitlab.com/dat.tang.gitlab/test-gitlab-ci/-/jobs/10780581182 (my test project, please reach out to me if you want to access it)
• Job definition - which is cloned from the actual release-environments-get-qa job in release-environments pipeline:

---
include:
  - project: 'gitlab-org/quality/pipeline-common'
    ref: '11.1.1'
    file: ci/base.gitlab-ci.yml

stages:
  - qa

release-environments-get-qa:
  stage: qa
  extends:
    - .qa-base
  timeout: 30m
  parallel: 3
  variables:
    QA_SCENARIO: "Test::Instance::Smoke"
    RELEASE: "registry.gitlab.com/gitlab-org/gitlab/gitlab-ee-qa:4004a2a454b"
    GITLAB_QA_OPTS: --address "https://gitlab.18-2-stable-security-get.env.release.gitlab.net"
    GITLAB_ADMIN_PASSWORD: "${GET_GITLAB_PASSWORD}"
    QA_PRAEFECT_REPOSITORY_STORAGE: "default"
    SIGNUP_DISABLED: "true"
    QA_NO_ADMIN_ENV: "false"
  before_script:
    - !reference [.qa-base, before_script]
    - echo "$CI_REGISTRY_PASSWORD" | docker login "$CI_REGISTRY" -u "$CI_REGISTRY_USER" --password-stdin
  tags:
    - gitlab-org-docker

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• This MR is backporting a bug fix, documentation update, or spec fix, previously merged in the default branch.
• The MR that fixed the bug on the default branch has been deployed to GitLab.com (not applicable for documentation or spec changes).
• The MR title is descriptive (e.g. "Backport of 'title of default branch MR'"). This is important, since the title will be copied to the patch blog post.
• This MR has a severity label assigned (if applicable).
• Set the milestone of the merge request to match the target backport branch version.
• This MR has been approved by a maintainer (only one approval is required).
• Ensure the e2e:test-on-omnibus-ee job has either succeeded or been approved by a Software Engineer in Test.

Note to the merge request author and maintainer

If you have questions about the patch release process, please:

• Refer to the patch release runbook for engineers and maintainers for guidance.
• Ask questions on the #releases Slack channel (internal only).