All pages need badging to indicate what products they are
applicable to.

Fix i18n link syntax on Repository Cleanup page

See merge request gitlab-org/gitlab!52529

Add incremental compiler to webpack dev server

See merge request gitlab-org/gitlab!52350

In order to have quicker compilations while developing we are adding an
incremental compiler to webpack to render routes on demand.

When the developer is working on the dev server and enables the
incremental compiler with DEV_SERVER_INCREMENTAL=true, the new
functionality is enabled.

The biggest problem to solve here: How can we _know_ which entry point
to render and which not? Our current webpack integration with rails
requires the webpack manifest to have a list of all existing entry
points. So our incremental compiler takes the following approach:

Every compilation of webpack will run `generateEntries` which generates
a list of all our entry points. In that function we are able to replace
all page specific entrypoints and point them to an empty file,
unless we explicitly want them to compile.

In the webpack-dev-server itself we register a middleware which keeps
track of all the page specific bundles requested. Whenever a page
specific bundle is requested that hasn't been requested before, we add
it to the list of bundles we want compiled.

This approach allows us to dynamically change the entry points without a
need to restart webpack alltogether _and_ it works with hot module
reloading.

Rather than pointing to a blank javascript we are pointing to one which
renders an overlay to let the user know that webpack compiles the page
for the first time.

Additionally we keep a history of requested routes in `tmp/cache` in
order to keep the list of compiled entry points between sessions. In a
next iteration we can add a bit of logic and e.g. remove entry points
the developer hasn't been visiting in a week.

First results are really promising (on my machine):
 - Memory consumption when idling: 1600MB => 340MB
 - Max memory: ~2200MB => ~1000MB
 - Initial Compilation time: 58s => 15s
 - Recompile afer a file change: 13s => 3s
 - Visiting a new page that hasn't been visited before, it takes about
   four seconds to reload the page, seven seconds to completely load the
   page.

Currently the technique still watches all of the source files, so
changing an unrelated file will trigger a recompilation. This is however
a minor caveat and the same behavior that we currently have, maybe we
can optimize in the future.

Add auto_delete_at to environments

See merge request gitlab-org/gitlab!52788

Apply new GitLab UI for input field in admin/broadcast_messages

See merge request gitlab-org/gitlab!52411

Pass the custom mapping fields to frontend

See merge request gitlab-org/gitlab!51982

Replaced bootstrap popover with GlPopover

See merge request gitlab-org/gitlab!49722

Mock help_popover in specs that
use full mount to test the content
of components

Add Quality as approver for feature specs

See merge request gitlab-org/gitlab!52523

When an MR diff is "Too Large", highlight it like other collapsed diffs

See merge request gitlab-org/gitlab!52146

Create constants for bv::show::modal and bv::hide::modal

See merge request gitlab-org/gitlab!52518

Clean up saas_manual_renew_button feature flag

See merge request gitlab-org/gitlab!52652

Updating tests and related files

Revisions to Create pages

See merge request gitlab-org/gitlab!52828

Word and line edits for Create pages, to bring down the number of
Vale warnings.

Resolve "Add subgroup_events column to web_hooks table"

See merge request gitlab-org/gitlab!52648

Remove obsolete DOMContentLoadedEventListener

See merge request gitlab-org/gitlab!52776

Edited UI text

See merge request gitlab-org/gitlab!52284

Related to: https://gitlab.com/gitlab-org/technical-writing/-/issues/321

Update Snowplow `gitlab_standard` schema docs

See merge request gitlab-org/gitlab!52741

Abstract out details of policy_helper

See merge request gitlab-org/gitlab!52714

Change Silver to Premium in API docs

See merge request gitlab-org/gitlab!52826

Show confirmation dialog when exiting pipeline editor

See merge request gitlab-org/gitlab!52458

If there are unsaved changes in the pipeline editor, the browser will
show a dialog box to confirm these changes before the user exits the
page.

Apply new GitLab UI for input field in user applications

See merge request gitlab-org/gitlab!52425

Apply new GitLab UI for input field in admin/labels

See merge request gitlab-org/gitlab!52413

Jira Connect app UI polish and improvements

See merge request gitlab-org/gitlab!52212

Move codequality feature flag to ci features

See merge request gitlab-org/gitlab!52618

Fix(subscribable banner): more explicit testing

See merge request gitlab-org/gitlab!52341

This updates tests to be explicit about what needs
to be set in order to trigger different links in
the banner

Add `source` to Snowplow StandardContext

See merge request gitlab-org/gitlab!52737

Geo: Remove unused BlobVerificationSecondaryService

See merge request gitlab-org/gitlab!52455

Add a blurb linking to a pairing session recording

See merge request gitlab-org/gitlab!52799

Update details about pipeline editor branch

See merge request gitlab-org/gitlab!52657