Create table `alerts_service_data`

See merge request gitlab-org/gitlab-ee!16607

This table contains data for the `AlertsService` avoiding the usage of
properties.

Add cop to check for GraphQL field descriptions (EE)

See merge request gitlab-org/gitlab-ee!16438

Add e2e tests for group audit logs

See merge request gitlab-org/gitlab-ee!16050

These can be fixed one by one, and until then, they are all
tagged to be ignored so we can backfill the descriptions in time.

- Fix typo
- Remove reference to outdated files
- Restrict directories to `app/graphql` and `ee/app/graphql` via
`.rubocop.yml`
- Correct all missing descriptions

Add a comment to disable to the cop for every missing GraphQL
description. When folks backfill the description to satisfy the cop,
they can remove the line.

Since we are now including arguments, and (probably) enums,
this is just called GraphQL Descriptions unless it proves
to be confusing.

Cluster environments BE/FE integration

See merge request gitlab-org/gitlab-ee!15515

Also adds the required qa-selectors

Avoid dns rebinding checks when the domain is whitelisted

Closes #31538

See merge request gitlab-org/gitlab-ee!16529

If the domain is whitelisted we skip dns rebinding checks as well
as local host checks

Ensure feature flags are set properly

Closes gitlab-org/quality/nightly#129

See merge request gitlab-org/gitlab-ee!16437

Also adds unit tests for Runtime::Feature.enabled?

EE: Show cluster link on job page

See merge request gitlab-org/gitlab-ee!16361

When the user has permissions (ie. maintainer) they can follow this link
to the cluster page. Otherwise they can always view this cluster name.
This is to implement
https://gitlab.com/gitlab-org/gitlab-ce/issues/55095 and helps users
debug cluster deployments.

This cluster detail will be used to show cluster link in the job output
as per https://gitlab.com/gitlab-org/gitlab-ce/issues/55095 . We needed
to create a new model here for ClusterBasicEntity as the only other
model ClusterStatus had much more data than necessary including nested
model lookups for applications.

Use a unique metric tag for each email handler

See merge request gitlab-org/gitlab-ee!16577

Otherwise there is a possibility that within the same
Sidekiq process, that same event with different
metrics_params will cause Prometheus to
throw an error, "labels must have the same signature"

Add end-to-end test for issue mention

See merge request gitlab-org/gitlab-ee!16485

Merge branch '65473-when-the-branch-name-is-a-divider-or-separator-the-project-home-page-cannot-display-the-branch-name-correctly-ee' into 'master'

EE Port of CE !32198

See merge request gitlab-org/gitlab-ee!16165

De-quarantine plan end-to-end test

Closes gitlab-org/quality/staging#68

See merge request gitlab-org/gitlab-ee!16526

Disable editing of the `License-Check` approval rule name.

See merge request gitlab-org/gitlab-ee!16149

* Allow editing during rule creation
* Add Changelog entry
* Updates the backend to prevent the `License-Check` rule name from
being edited.

Add e2e tests for project audit logs

See merge request gitlab-org/gitlab-ee!16012

Added E2E tests for SAST reports

Closes gitlab-org/quality/testcases#124 and gitlab-org/quality/testcases#131

See merge request gitlab-org/gitlab-ee!16415

Additionally updated fixture to provide SAST report

Notably, this changeset actually fixes ALL uses of gl_dropdown

Update explicit headers to new format

Cases tested:  
- Separator  
- Divider  
- Header

Basic Intent: Allow all branch names without accidentally creating
layout or backstage DOM. e.g. a branch named `separator` should never
create a separator `li` element.  

Ideally, there should never be a string that could cause this kind of 
conflict.  

Implementation: All of `GitLabDropdown.renderItem` is extracted to a 
standalone module.  

To render a divider or separator, consumers must now pass in an object 
like `{ "type": "divider" }` or `{ "type": "separator" }`   

Notable choices:  
- All of the functions have a cyclomatic complexity of 3 or less
    - See: https://en.wikipedia.org/wiki/Cyclomatic_complexity
    - Note the "Correlation to number of defects" section
    - While software complexity may not have a directly causal
      relationship with defects, less complex software is generally
      easier to reason about, and **may** reduce defects.
      I personally try to maintain complexity of no higher than 3.
- Everything other than the branch names fix matches past behavior 
exactly
    - Including:
        - Unused variables
        - Class list order

Enable mock setup to make onboarding development easier

See merge request gitlab-org/gitlab-ee!15492

- it used to be complicated to setup your local environment
  in order to work on the onboarding tour.  Full of
  temporary changes that would need backed out
- now we can work on it merely by enabling the Feature flag
  :user_onboarding

Add pod status for review-app release in debug

See merge request gitlab-org/gitlab-ee!16522

Remove EE specific checks

See merge request gitlab-org/gitlab-ee!16513

Remove orphaned project registries

Closes #13158

See merge request gitlab-org/gitlab-ee!15021

I have analyzed the execution of this test in the quarntine jobs
of some MRs, and in all of the executions that I looked it has
passed, so I'm de-quarantining it, but I'll keep an eye on it
in case it fails again.

[Backend] Step 3 API for trials

See merge request gitlab-org/gitlab-ee!16339