Remove deprecated state properties from license management's store

See merge request gitlab-org/gitlab!72284

Show all storage types in project's storage usage

See merge request gitlab-org/gitlab!72582

Add "Migrating features to Namespaces" section

See merge request gitlab-org/gitlab!72604

Add tests and documentation about how CI "extends" can be excluded

See merge request gitlab-org/gitlab!72511

Add cloak-startup class and apply to mobile overlay

See merge request gitlab-org/gitlab!71148

Correct suggestions for multiple comment boxes

See merge request gitlab-org/gitlab!72599

Deduplicate http transport creation

See merge request gitlab-org/gitlab!69471

Open Buy Minutes in new window if targeting CDot

See merge request gitlab-org/gitlab!72578

Add Sidekiq size limiter defaults to fake settings

See merge request gitlab-org/gitlab!72676

Create shared commit message field component

See merge request gitlab-org/gitlab!71522

Changelog: other

Add "will" to "ServiceDesk" string

See merge request gitlab-org/gitlab!72439

Make product_* values required and add TBD for missing product_section values

See merge request gitlab-org/gitlab!72585

We currently have several specific elements cloaked to prevent
flashing when using startup.css. This MR introduces a generic
class which can be applied to any element to achieve the same.

Here we apply it to the mobile top nav overlay to fix broken
rendering in certain race/network conditions.

Changelog: fixed

Merge branch '343394-ignore-plans-and-gitlab-subscriptions-in-cross-modification-check' into 'master'

Ignore plans and gitlab_subscriptions in cross modification check

See merge request gitlab-org/gitlab!72665

Add median lead time for changes to VSA

See merge request gitlab-org/gitlab!72283

These are needed when running background migration specs because those
execute Sidekiq client middleware and these use FakeApplicationSettings
with empty DB attributes

The RECEIVE_DELETE_LICENSE mutation did the same thing as
RESET_LICENSE_IN_MODAL, so this removes it. This also ensures that the
fetchLicenses action is properly dispatched. This was done via a
mediator, but we can simplify this by dispatching from the
receiveDeleteLicense action directly.

The RECEIVE_SET_LICENSE_APPROVAL mutation did the same thing as
RESET_LICENSE_IN_MODAL, so this removes it. This also ensures that the
fetchLicenses action is properly dispatched. This was done via a
mediator, but we can simplify this by dispatching from the
receiveSetLicenseApproval action directly.

This removes the following mutations:

* RECEIVE_DELETE_LICENSE_ERROR
* RECEIVE_SET_LICENSE_APPROVAL_ERROR

Both these mutations did the same thing as RESET_LICENSE_IN_MODAL which
can be committed instead.

This removes the loadManagedLicensesError property from the license management store.
This property isn't used anywhere, so it does not make sense to keep
maintaining it and the associated actions and mutations.

This removes the isSaving property from the license management store.
This property isn't used anywhere, so it does not make sense to keep
maintaining it and the associated actions and mutations.

This removes the isDeleting property from the license management store.
This property isn't used anywhere, so it does not make sense to keep
maintaining it and the associated actions and mutations.

Extract common DastSiteProfile mutation arguments

See merge request gitlab-org/gitlab!72469

Upgrade @gitlab/ui to v32.21.0

See merge request gitlab-org/gitlab!72195

Docs for removing cross-join redundant join

See merge request gitlab-org/gitlab!72170

Read more at https://gitlab.com/gitlab-org/gitlab/-/issues/343394 .

We are regularly seeing
CrossDatabaseModificationAcrossUnsupportedTablesError failures when we
call
[`Plan.default`](https://gitlab.com/gitlab-org/gitlab/-/blob/ad0085ce21be8d39b7598cb124adee7c75405922/app/models/plan.rb#L13)
and/or
[`Namespace#actual_plan`](https://gitlab.com/gitlab-org/gitlab/blob/master/ee/app/models/ee/namespace.rb#L180)
because both of these methods are lazily creating records.

At present we believe this is not strictly a problem that we need to
solve since it will is likely totally OK that creating a `plans` record
in the middle of a transaction related to `ci_pipelines` is not
important to rollback. Even more these lazy creations likely never need
to be rolled back anyway so we probably don't need to push these outside
the transactions.

Updated nav steps to match standards

See merge request gitlab-org/gitlab!72653

Add median lead time for changes to value stream analytics when it's
available for the current group or project.

Changelog: added
EE: true

Flag namespaces created during onboarding

See merge request gitlab-org/gitlab!71509