[Dequarantine] Plan 'creates an issue' 'closes an issue' & 'comments on an issue with an attachment'

What does this MR do?

E2E Test Failure issue(s)

The quarantine issue links to a production incident which has been closed.
https://gitlab.com/gitlab-com/gl-infra/production/-/issues/7099

Appears to be passing in the target environment qa-browser_ui-quarantine jobs

• https://ops.gitlab.net/gitlab-org/quality/preprod/-/jobs/7705692
• https://ops.gitlab.net/gitlab-org/quality/preprod/-/jobs/7697305
• https://ops.gitlab.net/gitlab-org/quality/preprod/-/jobs/7687395

# Test appears to consistently pass when run locally
export GITLAB_QA_ACCESS_TOKEN=${PRE_GITLAB_QA_ACCESS_TOKEN}
export GITLAB_USERNAME=${PRE_GITLAB_USERNAME}
export GITLAB_PASSWORD=${PRE_GITLAB_PASSWORD}
export QA_GITLAB_URL=${PRE_GITLAB_URL}

bundle exec rspec qa/specs/features/browser_ui/2_plan/issue/create_issue_spec.rb

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.