Quarantine stale and environment specific E2E specs

What does this MR do?

Quarantining stale and environment specific E2E specs to reduce the failure noise

• https://gitlab.com/gitlab-org/gitlab/-/issues/457496+ - fix is being worked on https://gitlab.com/gitlab-org/gitlab/-/issues/457496#note_1878491641, but waits for another MR - !150454 (comment 1878312453) - caused by FF enabled on Staging and Production, master has FF off so the test doesn't fail there.
• https://gitlab.com/gitlab-org/gitlab/-/issues/456092+ - flaky failures - see https://gitlab-qa-allure-reports.s3.amazonaws.com/e2e-package-and-test/master/1267067568/index.html#categories/36f1e0f69ea6dc83432af218c07f6b89/1ddc6e9c1c5f4546/history
• https://gitlab.com/gitlab-org/gitlab/-/issues/457099+ - 500 errors due to PATs issue, see https://gitlab.com/gitlab-org/gitlab/-/issues/457099#note_1877759101. Only happens on production from time to time and requires retry to unblock deployment.

E2E Test Failure issue(s)

• https://gitlab.com/gitlab-org/gitlab/-/issues/457496+
• https://gitlab.com/gitlab-org/gitlab/-/issues/456092+
• https://gitlab.com/gitlab-org/gitlab/-/issues/457099+

Check-list

• General code guidelines check-list
  • Code review guidelines
  • Style guides
• Quarantine test check-list
  • Follow the Quarantining Tests guide.
  • Confirm the test has a quarantine: tag with the specified quarantine type.
  • Note if the test should be quarantined for a specific environment.
  • (Optionally) In case of an emergency (e.g. blocked deployments), consider adding labels to pick into auto-deploy (Pick into auto-deploy priority1 severity1).
• Dequarantine test check-list
  • Follow the Dequarantining Tests guide.
  • Confirm the test consistently passes on the target GitLab environment(s).
• To ensure a faster turnaround, ask in the #quality_maintainers Slack channel for someone to review and merge the merge request, rather than assigning it directly.