Backport Deprecation task runner

See merge request gitlab-org/gitlab!70660

Replace "Any branch" with "All branches"

See merge request gitlab-org/gitlab!70552

Docs: Rearrange headings to avoid repetition

See merge request gitlab-org/gitlab!70680

Docs: Move the tbs section to the end of the doc

See merge request gitlab-org/gitlab!70678

Updated nav steps to match standards

See merge request gitlab-org/gitlab!70641

Updated nav steps to match standards

See merge request gitlab-org/gitlab!70644

Doc Consistency: integration/jira - integrations

See merge request gitlab-org/gitlab!70647

Add gitlab_slack_application_active count yamls

See merge request gitlab-org/gitlab!70496

Remove inclusion of unused strong memoize in alert presenter

See merge request gitlab-org/gitlab!70297

Fix stale MR discussion cache when current user role changes

See merge request gitlab-org/gitlab!69969

Doc Consistency: api/experiments.md

See merge request gitlab-org/gitlab!69790

Remove conditions on 2 User email validations

See merge request gitlab-org/gitlab!70549

Resolve "Doctor rake task reports GrafanaIntegration error if Grafana integration is configured on a project level"

See merge request gitlab-org/gitlab!69062

E2E: Group badge migration validation

See merge request gitlab-org/gitlab!70486

Docs: Update database.yml to include main: syntax

See merge request gitlab-org/gitlab!70654

Add security_orchestration_policy to pipeline source filter

See merge request gitlab-org/gitlab!69985

The scheduled scans that are triggered from the
security policy runs with source security_orchestration_policy
This commit adds Security Orchestration Policy as one of
the pipeline sources in the filter.

EE: true
Changelog: added

In https://gitlab.com/gitlab-org/gitlab/-/merge_requests/69642, we
fixed the case when note's author role changes.

It's also possible that the MR discussions cache will be stale if
the current_user role has changed.

For example, current user was a maintainer and viewed the MR page
with discussions. That user will be able to resolve comments. When
that user gets demoted to Guest, for example, they shouldn't be
able to resolve threads anymore.

Currently, that will only affect the notes they authored. For
other notes, the "Resolve" button will still show.

This fix adds the max access of the current user to the cache
context so when it changes, the cache will be invalidated too.

Upgrade grape-entity gem

See merge request gitlab-org/gitlab!70403

MilestoneWildcardIdEnum upcoming description matches behavior

See merge request gitlab-org/gitlab!70536

Update MetaData of Secret Management Docs to Configure

See merge request gitlab-org/gitlab!70628

Changelog: fixed

Refactor package factories

See merge request gitlab-org/gitlab!70445

Make DAST more easily extendable

See merge request gitlab-org/gitlab!70138

Drop support for `data-track-event`

See merge request gitlab-org/gitlab!70234

Update dependency eslint-import-resolver-jest to v3.0.2

See merge request gitlab-org/gitlab!69997

Update QA to Chemlab 0.8

See merge request gitlab-org/gitlab!70440

Add additional properties to policy_details helper

See merge request gitlab-org/gitlab!70553

Move web_terminal_spec E2E test to CE folder

See merge request gitlab-org/gitlab!70337