E2E: Quarantine Merge with Code Owner Specs

What does this MR do?

Quarantines the following E2E tests until these failures can be investigated in order to help reduce noise in the pipelines.

• ee/browser_ui/3_create/repository/merge_with_code_owner_in_subgroup_spec.rb | Create Codeowners when the project is in a subgroup and the code owner is the root group behaves like code owner merge request is approved and merged
• ee/browser_ui/3_create/repository/merge_with_code_owner_in_root_group_spec.rb | Create Codeowners when the project is in the root group and the code owner is the root group behaves like code owner merge request is approved and merged

E2E Test Failure issue(s)

• #422935 (closed)
• #422975 (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.