E2E: Quarantine Vulnerability Specs

What does this MR do?

This MR quarantines the following specs:

• qa/qa/specs/features/ee/browser_ui/10_govern/change_vulnerability_status_spec.rb
• qa/qa/specs/features/ee/browser_ui/10_govern/fix_vulnerability_workflow_spec.rb
• qa/qa/specs/features/ee/browser_ui/10_govern/vulnerability_management_spec.rb (test case https://gitlab.com/gitlab-org/gitlab/-/quality/test_cases/383756)

A recent UI change has removed all data-qa-selectors that was once associated with the Status dropdown and its dropdown items. The dropdown items used to dynamically create the selectors, but now that the UI is using a GlCollapsibleListbox from gitlab-ui instead, it will require a bit more thought on how we want to update the tests. (See #411937 (comment 1394719427))

E2E Test Failure issue(s)

• #411937 (closed)
• #411939 (closed)
• #411938 (closed)

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.