[E2E] Quarantine Govern Security Reports

What does this MR do?

[E2E] Quarantine Govern Security Reports due to consistent failures cross jobs in master pipelines. These failures don't impact every job, in the pipeline, but on each pipeline a number of them appear so we're having constant noise from the pipelines with no clear reason as to why.

These errors have not been reproduced locally as of now, so quarantining until we have a better picture as to why these are failing.

E2E Test Failure issue(s)

• Multiple failures in Failure in ee/browser_ui/1... (#420136 - 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.