E2E: Quarantine recovery_alert_closes_correct_incident_spec

What does this MR do?

Both HTTP and Prometheus recovery alerts are experiencing a transient bug with delays in resolving their associated incidents: #395512 (comment 1337325300)

This first was noticed with HTTP endpoint integration in nightly pipelines. Now, it is affecting Prometheus integration mostly in main, though the issue can occur less frequently in live environments: #408321 (closed)

This MR quarantines the entire spec in all environments and links the issue to the original bug.

E2E Test Failure issue(s)

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.