Quarantine Gitaly Cluster replication queue E2E due to timing out

What does this MR do?

I have an MR open !86322 (merged) but I was rerunning it locally and seeing this still fail.
Given that it's likely slowing the pipeline down quite a bit due to the infinite loop lets quarantine it until I figure out how to proceed.

E2E Test Failure issue(s)

https://gitlab.com/gitlab-org/gitlab/-/quality/test_cases/347829

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).
    • (Optionally) Trigger a manual GitLab-QA pipeline against a specific GitLab environment using the RELEASE variable from the package-and-qa job of the current merge request.
• To ensure a faster turnaround, ask in the #quality Slack channel for someone to review and merge the merge request, rather than assigning it directly.