Revert "Quarantine jira integration tests"

Description of the test

In !207821 (merged), we disabled the E2E tests for the Jira integration due to !206815 (merged) changing the Jira integration to only work with Jira Cloud. The affected E2E tests only work with Jira Server.

Since then, we have added !208859 (merged) which restores Jira Server compatibility with the Jira integration, therefore we should take the affected E2E tests out of quarantine.

How to set up and validate locally

# Obtain credentials from 1Password (JIRA docker host)
❯ export QA_JIRA_ADMIN_USERNAME=xxxxxx
❯ export QA_JIRA_ADMIN_PASSWORD='xxxxxxxxx'
❯ export JIRA_HOSTNAME=http://localhost:8080

❯ docker run -d \
  --name jira-server \
  -p 8080:8080 \
  registry.gitlab.com/gitlab-org/gitlab-qa/jira-gitlab:8.8-project-and-issue

❯ gitlab-qa Test::Instance::Any EE http://172.16.123.1:3000 -- qa/qa/specs/features/ee/browser_ui/1_manage/integrations/jira_issues_list_spec.rb --tag orchestrated

❯ gitlab-qa Test::Instance::Any EE http://172.16.123.1:3000 -- qa/qa/specs/features/ee/browser_ui/18_security_risk_management/vulnerabilities_jira_integration_spec.rb --tag orchestrated

Checklist

• Confirm the test has a testcase: tag linking to an existing test case in the test case project.
• Note if the test is intended to run in specific scenarios. If a scenario is new, add a link to the MR that adds the new scenario.
• Follow the end-to-end tests style guide and best practices.
• Use the appropriate RSpec metadata tag(s).
• Most resources will be cleaned up via the general cleanup task. Check that is successful, or ensure resources are cleaned up in the test:
  • New resources have api_get_path and api_delete_path implemented if possible.
  • If any resource cannot be deleted in the general delete task, make sure it is ignored.
  • If any resource cannot be deleted in the general delete task, remove it in the test (e.g., in an after block).
• Ensure that no transient bugs are hidden accidentally due to the usage of waits and reloads.
• Verify the tags to ensure it runs on the desired test environments.
• If this MR has a dependency on another MR, such as a GitLab QA MR, specify the order in which the MRs should be merged.
• (If applicable) Create a follow-up issue to document the special setup necessary to run the test: ISSUE_LINK
• If the test requires an admin's personal access token, ensure that the test passes on your local environment with and without the GITLAB_QA_ADMIN_ACCESS_TOKEN provided.