Merge branch '241912-remove-v-html-from-ee-app-assets-javascripts-environments-components-deploy_board_component' into 'master'

Remove v-html from ee/app/assets/javascripts/environments/components/deploy_board_component.vue

Closes #241912

See merge request gitlab-org/gitlab!41521

Fix some broken links

See merge request gitlab-org/gitlab!42245

Document use of environment_url.txt in API Fuzzing

See merge request gitlab-org/gitlab!41523

Fix broken anchors in the secrets documentation

Closes #249172

See merge request gitlab-org/gitlab!42244

Add release `upcoming_release` field to GraphQL

See merge request gitlab-org/gitlab!41183

This commit adds the boolean "upcoming_release" field to the GraphQL
endpoint.

Populate an Incident's severity when it's created from an Alert

Closes #238571

See merge request gitlab-org/gitlab!42072

Signed-off-by: Rémy Coutable <remy@rymai.me>

Migrate GlNewDropdownDivider to GlDropdownDivider

See merge request gitlab-org/gitlab!42145

Retry DAST jobs

See merge request gitlab-org/gitlab!41574

Tweak Sentry GRPC error processor

See merge request gitlab-org/gitlab!42199

Docs: Update metadata with Style Guide group link

See merge request gitlab-org/gitlab!42235

CI Secrets documentation

See merge request gitlab-org/gitlab!38552

and Vault integration.

Related to https://gitlab.com/gitlab-org/gitlab/-/issues/28321
and https://gitlab.com/gitlab-org/gitlab/-/issues/218746.

Report BatchNotResetError to Sentry only after retries

See merge request gitlab-org/gitlab!42074

Only one report will be sent to Sentry, containing data
about failing batches and not each time an error is rescued.
This removes noise from Sentry when a worker succeeds on
retry.

Store Instance Statistics measurements periodically

See merge request gitlab-org/gitlab!41300

This change will periodically count various objects in the database and
store the data in a database table.

GitLab UI doesn't export `GlNewDropdownDivider` anymore, this updates
all imports to use `GlDropdownDivider` instead,

Docs: Updated template guidelines

See merge request gitlab-org/gitlab!41839

Change name of GitLab Instance Administrators group

See merge request gitlab-org/gitlab!41684

Docs: Removed outdated metadata

Closes #247288

See merge request gitlab-org/gitlab!42136

Related to: https://gitlab.com/gitlab-org/gitlab/-/issues/247288

Load Issue Sidebar Data through startup.js

See merge request gitlab-org/gitlab!42206

Add incident label for manually created incident issues

See merge request gitlab-org/gitlab!41598

Fail pipeline early when there is rspec failure related to MR changes

See merge request gitlab-org/gitlab!41081

Add rspec fail-fast job
- This job runs rspec on test files detected by
  the job `detect-tests`.

Add fail-pipeline-early job
- This job cancels the current pipeline in order
  to provide fast feedback upon test failure.
  This happens when the `rspec fail-fast` jobs has failed.

Add toggle to enable `rspec fail-fast`
- The rspec-fail-fast and fail-pipeline-early jobs
  will only be created if the RSPEC_FAIL_FAST_ENABLED variable
  is "true".
- Using this flag, we can experiment with this pipeline
  change with more control.

Add option to skip rspec fail-fast
- Using MR title SKIP RSPEC FAIL-FAST
- Using dont-interrupt-me job

Add Enum support for `deprecated` argument

See merge request gitlab-org/gitlab!41630

`ruby-graphql` supports

https://gitlab.com/gitlab-org/gitlab/-/merge_requests/27464 added support
for a custom `deprecated` keyword for `field` to allow us to specify the
milestone that a field was deprecated in a structured way.

Enum values are also able to be deprecated. This change adds support for
enum values.

Also see: https://gitlab.com/gitlab-org/gitlab/-/issues/199952

Hide confirmation modal after closing a blocked issue

See merge request gitlab-org/gitlab!42068

GraphQL - Expose group memberships under group

See merge request gitlab-org/gitlab!39331

- Use GroupMembersFinder

Previously, we've created and applied the "incident" label
only when calling the `IncidentManagment::Incidents::CreateService`
explicitly. After we've added the issue type "incident" incidents
can be created/updated using the `Issues::Create/UpdateService`.
Those services did not apply this label.

This commit moves the code which applies the label close to the
`Issue` services to make sure we are labeling all incidents with
the "incident" label correctly.

Reduce the total amount of factories from 260 to 43 cutting
the total amount of events in half.

Queries saved: 6121