When an admin saves an instance-level integration, they will have two
options that will propagate the settings differently.

- Apply changes to inherited integrations:
  - Updates integration for inherited projects
  - Creates integrations for projects without integrations
- Apply changes to all integrations:
  - Updates integration for all projects
  - Creates integrations for projects without integrations

Fixes Monaco library loading on merge requests

See merge request gitlab-org/gitlab!32540

Docs: Added metadata for Package

See merge request gitlab-org/gitlab!32608

Merge branch 'update-slot-syntax-of-ee/app/assets/javascripts/vue_shared/security_reports/components/modal.vue' into 'master'

Update deprecated slot syntax in` ee/app/assets/javascripts/vue_shared/security_reports/components/modal.vue`

See merge request gitlab-org/gitlab!31966

Update deprecated slot syntax in` ee/app/assets/javascripts/vue_shared/security_reports/components/modal.vue`

Stop reusing design component on route change

See merge request gitlab-org/gitlab!32447

- Fixed router spec

Remove unused monitoring bundle file

See merge request gitlab-org/gitlab!32389

Change link for Threat Monitoring docs to docs.gitlab.com

See merge request gitlab-org/gitlab!32576

Merge branch '205401-cannot-view-content-of-moved-file-without-changes-in-merge-request' into 'master'

Add UI to load the full file for `renamed`-type files

See merge request gitlab-org/gitlab!28448

Improve danger bot layout for telemetry review

Closes #217719

See merge request gitlab-org/gitlab!32071

Minor improvements to Puma docs

See merge request gitlab-org/gitlab!32621

Add describe blocks to emails_on_push_service_spec

See merge request gitlab-org/gitlab!32439

Revert '207250-allow-admins-to-modify-mr-approval-settings..' to 'master'

See merge request gitlab-org/gitlab!32610

Add truncation for the environment dropdown

See merge request gitlab-org/gitlab!32267

Make text property optional for custom var types

See merge request gitlab-org/gitlab!32596

Fix leaky constant in sidekiq middleware client metric specs

See merge request gitlab-org/gitlab!32108

Add front matter to vale subst rules

Closes #218431

See merge request gitlab-org/gitlab!32616

Step 1 - Clean up some collapsible_panel things

See merge request gitlab-org/gitlab!32464

Add explicit schema version check

See merge request gitlab-org/gitlab!32524

Resolve "Improve performance of Search API (Advanced): merge_requests scope"

See merge request gitlab-org/gitlab!30546

Create MergeRequestPreloader for Search API
to be used with merge_requests scope.

The preloader lazily loads attributes using
BatchLoader and utilizes the lazy attributes in
the MergeRequestBasic Entity if lazy_load option
is set. This improves response times by avoiding
N+1 queries.

Revert "Merge branch '207250-allow-admins-to-modify-mr-approval-settings-at-the-project-level-after-enabling-them-in' into 'master'"

This reverts merge request !30358

Persist banner dismissal

See merge request gitlab-org/gitlab!31894

Also improves wording of sentence.

The monitoring_bundle_with_alerts was a quick fix for migrating custom
metrics to CE, this is file is not needed anymore.

Add 'style guide' to Vale substitution rules

See merge request gitlab-org/gitlab!32614

Docs: Added metadata for Release stage

See merge request gitlab-org/gitlab!32607

Docs: mark GitLab Status Pages as Ultimate

See merge request gitlab-org/gitlab!32482

And: reduce all the possible state combinations to a FSM

Per design review, this component needed a bunch more
interactivity. Most critically, around displaying and responding
to a load error.

Rather than set a bunch of flags and toggle various elements
based on a collection of booleans, I think it's much easier to
reason about this component if it has a Finite State Machine
representing its possible states and transitions between them.

The two notable logic additions here are a rudimentary FSM
(`transition`) and a state checker (`is`).

`transition` defines all the ways the component can go from
one state to another. If a transition is attempted that doesn't
match one of these declared transitions, it does nothing.
Every transition always results in a declared state.
these two things combined make it much easier to reason
about what the component should look like at any given
moment.

Other than the state machine (which should be replaced with
something like @xstate/fsm), the rest of these changes are
text changes from UX/technical writing review.

Also updates other components that eventually
use the same component

Per our design docs, global flash messages aren't appropriate
in this context (or virtually anywhere!), so there's no reason
to catch this error here.

Change codeblock fence languages to full name 2

See merge request gitlab-org/gitlab!32502