This commit adds documentation coverage for the apply
suggested changes custom commit message configuration
and its API counterpart.

This commit adds the capability to define a custom
commit message, which is used when a change
suggestion on a merge request is applied. The
configuration is done on a project settings level and
supports free text with GitLab variables. The old
hardcoded commit message is used as a fallback
option.

Update rack-cors to 1.0.6

Closes #39143

See merge request gitlab-org/gitlab!22809

Container Expiration Policies recurring jobs

See merge request gitlab-org/gitlab!21593

Add missing argument to performance bar page object method

See merge request gitlab-org/gitlab!22798

Add count argument to has_detailed_specs method
Refactor performance_bar_spec

Update Code Quality docs about the new versioning scheme

See merge request gitlab-org/gitlab!21934

Cache webpack loaders in CI

See merge request gitlab-org/gitlab!22204

Move cluster dropdown component one level up

See merge request gitlab-org/gitlab!22715

fix docs: remove duplicate `with your'

See merge request gitlab-org/gitlab!22816

Remove feature flag for import graceful failures

See merge request gitlab-org/gitlab!22707

Make Sidekiq timestamps consistently ISO 8601

Closes #194116

See merge request gitlab-org/gitlab!22750

Code Review analytics skeleton

See merge request gitlab-org/gitlab!22480

Migrate project_id dropdown tests to jest

See merge request gitlab-org/gitlab!22609

Make BackgroundMigrationWorker backward compatible

See merge request gitlab-org/gitlab!22271

Fix spacing between errors in Geo Node Cards

Closes #196075

See merge request gitlab-org/gitlab!22718

Replace usaged in geo/node/projects

https://gitlab.com/gitlab-org/gitlab/merge_requests/22718

Move common request specs into shared_examples

See merge request gitlab-org/gitlab!22428

* In preparation for the specs being reused, move them into
shared_examples.

Previously when an exception occurred in Sidekiq, Sidekiq would export
logs with timestamps (e.g. created_at, enqueued_at) in floating point
seconds, while other jobs would report in ISO 8601 format. This
inconsistency in data types would cause Elasticsearch to drop logs that
did not match the schema type (date in most cases).

This commit moves the responsibility of formatting timestamps to the
Sidekiq JSON formatter where it properly belongs. The job logger now
generates timestamps with floats, just as Sidekiq does. This ensures
that timestamps are manipulated only in one place.

See https://gitlab.com/gitlab-com/gl-infra/infrastructure/issues/8269

Fix broken shallowMount with GlModal

See merge request gitlab-org/gitlab!22797

Document propagated gemnasium db variables

See merge request gitlab-org/gitlab!22670

Clarify IE11 has no supported previous version

See merge request gitlab-org/gitlab!22343

Give identical Ruby metrics same description

See merge request gitlab-org/gitlab!22562

Enable Instance level Security Dashboard feature by default

See merge request gitlab-org/gitlab!18008

Part of the [Instance Security Dashboard MVC][1].

This adds documentation for the Instance Security Dashboard, and enables
the `security_dashboard` feature flag by default.

[1]: https://gitlab.com/gitlab-org/gitlab/issues/6953

Add support to import award emojis for missing entities

See merge request gitlab-org/gitlab!22493

Added changelog entry for the fix
Corrected typo in spec description

**How?**
Making this spec a full mount instead.

**Why?**
The test was failing with an error in our
GlModal that `$refs.modal.show` was not
a function. This is because shallowMount
will stub the internal b-modal. So that we're
not messing with internals too much, let's just
do a full mount here :)