Add options for clearing cache to the docs

See merge request gitlab-org/gitlab!79057

CTRT edits for group migration doc

See merge request gitlab-org/gitlab!76897

Fix DAST On-Demand API Scan template

See merge request gitlab-org/gitlab!76491

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

* replaces the DastSiteProfile ci variable from `DAST_API_SPECIFICATION` 
  to `DAST_API_OPENAPI` as suggested here
  https://gitlab.com/gitlab-org/gitlab/-/merge_requests/73564#note_738732568
* remove the `GIT_STRATEGY: none` as suggested here
  https://gitlab.com/gitlab-org/gitlab/-/issues/347255#note_754003722

Geo: Remove feature flag geo_treat_missing_files_as_sync_failed

See merge request gitlab-org/gitlab!78238

Revert "Merge branch 'wc-gitaly-keepalive-limit' into 'master'"

See merge request gitlab-org/gitlab!78966

E2E: Fix stale merge request import spec

See merge request gitlab-org/gitlab!79044

Swap OncallSchedule services to inherit from BaseProjectService

See merge request gitlab-org/gitlab!78317

Update usage of newly created gitlab-ui CSS utilities

See merge request gitlab-org/gitlab!78922

Add missing Git authentication support for group level bot build tokens

See merge request gitlab-org/gitlab!78595

Replace owner with first_owner in feature specs

See merge request gitlab-org/gitlab!78757

Remove unnecessary index on cluster_agent_tokens

See merge request gitlab-org/gitlab!78348

Disable sandboxed_mermaid feature flag by default

See merge request gitlab-org/gitlab!79045

Fix typo in message

See merge request gitlab-org/gitlab!78900

Some error messages contained a wrong spelling of `occurred`
MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/78900/

Changelog: fixed

Remove instructions to install Agent if KAS is not set up

See merge request gitlab-org/gitlab!78168

Replace owner with first_owner in finder specs

See merge request gitlab-org/gitlab!78855

Merge Requests: sort alphabetically

See merge request gitlab-org/gitlab!76472

Replace usage of find/findAll in ee/spec/frontend/threat_monitoring

See merge request gitlab-org/gitlab!78643

Backport unit tests changes from Apollo migration MR

See merge request gitlab-org/gitlab!77990

Added `waitForPromises` to unit tests to work with modified helper

Merge branch '350286-experiment-cleanup-redirect-in-app-trial-users-to-the-feature-that-they-requested-the-trial' into 'master'

Redirect in-app trial users to the feature

See merge request gitlab-org/gitlab!78917

Changelog: added
EE: true

Changelog: removed

Added GitLab Runner to steps

See merge request gitlab-org/gitlab!78752

Replace deprecated usage of find/findAll in ee/spec/frontend/security_dashboard

See merge request gitlab-org/gitlab!78633

* migrate to proper use of findComponent/findAllComponents

Cache CI expire_in parsing

See merge request gitlab-org/gitlab!78953

Fix CI instance variable cache misses

See merge request gitlab-org/gitlab!78944

Applied .container-fluid .container-limited classes

See merge request gitlab-org/gitlab!78676

Resolves https://gitlab.com/gitlab-org/gitlab/-/issues/350469

Add breaking change values to removals

See merge request gitlab-org/gitlab!78943

When a removal is in the 14_0 directory, assume it was a breaking change

Based on this comment: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/78716\#note_817172127
Decided to update this phrase because it makes more sense this way

Remove PagesUpdateConfigurationWorker logic

See merge request gitlab-org/gitlab!78449

Previously the CI processor spent a surprising amount of time
validating the `expire_in` field for each build in the pipeline. It
turns out `ChronicDuration.parse` can be expensive because it uses
regular expressions and ActiveSupport numeric conversions.

We observe that builds often use a small set of `expire_in` values, so
we can cache the result of a previous validation.

For a pipeline like `gitlab-org/gitlab` that has 200 builds with 8
different `expire_in` values, we see a 28x improvement:

```
Calculating -------------------------------------
                 old     1.000  i/100ms
                 new    14.000  i/100ms
-------------------------------------------------
                 old      5.275  (± 0.0%) i/s -     27.000
                 new    149.409  (± 5.4%) i/s -    756.000

Comparison:
                 new:      149.4 i/s
                 old:        5.3 i/s - 28.32x slower
```

Relates to https://gitlab.com/gitlab-org/gitlab/-/issues/322386

Changelog: performance