Upgrade cilium helm charts in cluster_management template

See merge request gitlab-org/gitlab!65982

Deprecate monthly incident_sla_enabled metric

See merge request gitlab-org/gitlab!66025

Refactor group scope menu

See merge request gitlab-org/gitlab!65724

Update QA test execution context selection docs

See merge request gitlab-org/gitlab!61319

Revise group Pages size UI text

See merge request gitlab-org/gitlab!65862

Remove securityScansSucceeded from DevOps Adoption

See merge request gitlab-org/gitlab!66291

Add ConfigureSecurityAnalyzer superclass [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!65965

Remove old license page logic

See merge request gitlab-org/gitlab!65978

Add Cop that enforces worker data_consistency [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!65341

Use configured browser locales for date formatting

See merge request gitlab-org/gitlab!65740

This allows us to decide a little better what a user wants as a locale
for using with the Intl browser APIs. If they have set their GitLab to
a language, it will check whether `navigator.languages` contains
matching ones. This function always adds `en` as a fallback in order to
have date renders if all fails before it.

- Example one: GitLab language is `en` and browser languages are:
  `['en-GB', 'en-US']`. We would choose `['en-GB', 'en-US', 'en']` as
  the preferred locales, the Intl APIs would try to format first as
  British English, if that isn't available US or any English.
- Example two: GitLab language is `en` and browser languages are:
  `['de-DE', 'de']`. We would choose `['en']`, so the Intl APIs
  would prefer English formatting in order to not have German dates
  mixed with English GitLab UI texts.
  If the user wants for example British English formatting (24h, etc),
  they could set their browser languages to `['de-DE', 'de', 'en-GB']`.
- Example three: GitLab language is `de` and browser languages are \
  `['en-US', 'en']`. We would choose `['de', 'en']`, aligning German
  dates with the chosen translation of GitLab.

This function is currently only used for absolute dates:
- https://gitlab.com/gitlab-org/gitlab/-/merge_requests/65570

Changelog: changed

Make data_category required

See merge request gitlab-org/gitlab!66317

The securityScansSucceeded query was causing a timeout error. Also,
it has already been mostly replaced with queries for individual scan
types. This removes the column from DevOps adoption, and removes the
data collection from the snapshot. This does not remove the column,
because this is an urgent change, so that will be removed in a
follow-up MR.

Changelog: removed
EE: true

Add ref to the Pipeline schema for the GraphQL API

See merge request gitlab-org/gitlab!66241

Switch over commit RPCs to use ListCommits

See merge request gitlab-org/gitlab!65468

Pin version of package hunter client

See merge request gitlab-org/gitlab!66152

Update policy for granting `build_read_container_image` to users

See merge request gitlab-org/gitlab!65961

Don't compress job arguments twice

See merge request gitlab-org/gitlab!66320

Don't fail db restore for warnings

See merge request gitlab-org/gitlab!66094

Update dependency eslint to v7.31.0

See merge request gitlab-org/gitlab!66338

Rename doc links to service ping and refactor js

See merge request gitlab-org/gitlab!66346

Geo: Fix snippet verification by replicating the HEAD ref

See merge request gitlab-org/gitlab!65783

Support reindexing unique indexes

See merge request gitlab-org/gitlab!65966

Enable load balancing for Jira Connect workers

See merge request gitlab-org/gitlab!66286

Update OIDC topic for current conventions

See merge request gitlab-org/gitlab!66348

When a job is scheduled in the future, it runs through the client
middleware twice. Once on scheduling, once when queueing.

Since the `args` key of the job would already be compressed at this
time, we don't need to compress it some more. Doing so would cause the
decompression to fail on the serverside.

This enables >=PG12-compatible reindexing behavior leveraging
REINDEX CONCURRENTLY which supports reindexing unique indexes.

Changelog: other

This ensures developers consider scalability and immediacy
trade-offs by either using or not using the DB primary.

E2E: Add environment info to allure report

See merge request gitlab-org/gitlab!66139

Docs: Add notes on removing more than 1 license

See merge request gitlab-org/gitlab!66341

Update upload blob modal to use constants

See merge request gitlab-org/gitlab!65907

Docs: explain Jenkins integration recommendation

See merge request gitlab-org/gitlab!66038