Revert post-deploy migration

See merge request gitlab-org/gitlab!44591

Merge branch '262481-move-handlers-outside-of-domcontentloaded-app-assets-javascripts-pages-projects-packages' into 'master'

Handlers outside of DOMContentLoaded: /packages/show

See merge request gitlab-org/gitlab!44576

Expose scan object in unsaved findings

See merge request gitlab-org/gitlab!44274

Enable sorting vulnerabiliies by state

See merge request gitlab-org/gitlab!42974

Minor refactor analytics/cycle_analytics feature specs

See merge request gitlab-org/gitlab!44412

Moves the remaining analytics/cycle_analytics specs into the
groups folder alongside the others.

Deletes the old directory

Update dependency dompurify to ^2.1.1

See merge request gitlab-org/gitlab!44586

List personal info fields in profile documentation

See merge request gitlab-org/gitlab!44523

Previously the documentation for the User's Edit Profile page lacked
detail on which "personal information" fields were available. This adds
a rough list.

Update and expose board labels in graphql

See merge request gitlab-org/gitlab!44204

Alert integrations table

See merge request gitlab-org/gitlab!44181

This has failed in a GitLab.com deploy:
https://gitlab.com/gitlab-com/gl-infra/production/-/issues/2802

Store Security::Scan and Security::Finding entries

See merge request gitlab-org/gitlab!42634

Only allow multiple reviewers in paid tiers

See merge request gitlab-org/gitlab!44097

Mark sidekiq queues that require local shared disk access

See merge request gitlab-org/gitlab!44504

* Queues marked with this require some form of access for data
that is shared among various components.  An example might be that the
queue writes data to a local directory that is quickly displayed to the
user.
* In scenarios where large installations exist, this requires some form
of shared stored, commonly NFS, to be configured where sidekiq can write
the data, but then a set of web front ends have the same NFS share such
that they are capable of reading that data and vice versa.
* This commit marks all queues _known_ to have such a dependency
* As this dependency is removed, this tag should be removed

Resolve mock_data TODO

See merge request gitlab-org/gitlab!44364

Merge branch '262491-move-handlers-outside-of-domcontentloaded-app-assets-javascripts-pages-projects-registry' into 'master'

Handlers outside of DOMContentLoaded: /registry/repositories/index

See merge request gitlab-org/gitlab!44579

Create auto-fix user callout

See merge request gitlab-org/gitlab!42405

Created the auto-fix user callout that shows up in the project security
dashboard (unless previously dismissed).

Allow for boards to be updated with labels as well as expose board
labels in graphql.

Merge branch '235391-support-group-milestones-to-be-associated-with-project-releases-in-api-2' into 'master'

Add missing milestone tests to Release API

See merge request gitlab-org/gitlab!44157

Resolve "MR Analytics: Add datepicker to filter bar"

See merge request gitlab-org/gitlab!43814

Add a date range picker to the MR Analytics page.
Change the date range util to include start and end dates.

Exclude bots from licensed user count

See merge request gitlab-org/gitlab!42034

Remove item when dismissed on security dashboard if no longer in filter

See merge request gitlab-org/gitlab!43468

Hide vulnerability after dismissal if not in filter list and process
each dismissal instead of stopping after the first failure

Add client side connection-pool documentation

See merge request gitlab-org/gitlab!42861

This explains how we manage the client side connection-pool size, and
what can be done to mitigate an incident if we were to notice it's
incorrectly sized.

Update the Gitaly section to be the same on all pages

See merge request gitlab-org/gitlab!44474

For consistency's sake, it would be good for the reference architecture
pages to reflect the same information.

Add ability to sort vulnerabilities by state

See merge request gitlab-org/gitlab!42973

This change adds ability to sort vulnerabilities by state in
GraphQL.

These new service classes will save the entries of Security::Scan and
Security::Finding models grouped by same report kind to optimize memory
usage while marking the duplicated findings withing the same group.

Once we deploy this new worker, security scan entries and findings will
be saved by the new worker class.
We will stop using the old worker but we can't remove it completely as
there might be some jobs enqueued for the worker.

Introduce required_code_owners_sections table

See merge request gitlab-org/gitlab!43573

Move Feature Flag Api and Controllers to Core RUN AS-IF-FOSS

See merge request gitlab-org/gitlab!44093