Quarantine composer_registry_spec in live envs due to broken test

What does this MR do?

This test was de-quarantined in !142627 (comment 1741084315) However the underlying issue is still present and we now have a new set of failures as noted in #439376 (closed)

E2E Test Failure issue(s)

• Failure in browser_ui/5_package/package_registr... (#439376 - 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.