Default test cases feature flag to on

See merge request gitlab-org/gitlab!47948

Added the essential User Timings to WebIDE

See merge request gitlab-org/gitlab!47934

Update todo vue tooltip with gl-tooltip

See merge request gitlab-org/gitlab!47810

Implement CE security_reports Vuex store

See merge request gitlab-org/gitlab!47556

This creates a CE security_reports store that is a subset of the EE
version. This subset is roughly the minimum necessary to render counts
on the CE security MR widget. See this [epic][1] for more details about
the overall direction.

The majority of this change is just existing code that's been moved
and/or refactored. The only _genuinely_ new piece of code is the new
store's entry point:
`app/assets/javascripts/vue_shared/security_reports/store/index.js`.

Since the CE version only supports SAST and Secret Detection, this MR
also refactored the getters to generalise over an array of report types,
rather than hard code them all into every getter. This means that these
getters can be shared as-is between CE and EE, and behave correctly due
to the `reportTypes` field added to the state of both stores. These
getters are tested in both CE and EE, to verify the different behaviour
based on the available report types.

The `noBaseInAllReports` getter turned out not to be used anywhere, so
it was deleted.

Two existing getters, `anyReportHasIssues` and `areAllReportsLoading`
didn't have tests, so tests were added for them in both CE and EE.

Since the getters now more explicitly depend on the report types
installed in the store, constants were extracted to make their
connection explicit, and reduce the chance that typos would lead to
runtime errors.

The vulnerability severity constants were moved to a common location in
CE.

The definitions of the `LOADING`, `SUCCESS` and `ERROR` constants were
deleted from the `security_reports` directory, since their definitions
already exist in the `~/reports/constants.js` file. These constants are
intended to be used with/by the `ReportSection` component, so it makes
sense not to redefine them elsewhere.

Part of https://gitlab.com/gitlab-org/gitlab/-/issues/273423.

[1]: https://gitlab.com/groups/gitlab-org/-/epics/4394

Test Cases Documentation

See merge request gitlab-org/gitlab!47685

Never link to /helpl, and internal links must be relative

Update Gitaly version

See merge request gitlab-org/gitlab!48028

Add ExportedProtectedBranch model for Import/Export

See merge request gitlab-org/gitlab!47181

Fix flaky VSA tests

See merge request gitlab-org/gitlab!47915

Refactor Snippet#blobs method

See merge request gitlab-org/gitlab!48029

Start using smaller docs lint image for link tests

See merge request gitlab-org/gitlab!47745

Copy edit yaml ref, focusing on gerunds

See merge request gitlab-org/gitlab!47264

Remove append/prepend 15 and 20 utility classes

See merge request gitlab-org/gitlab!47942

Create compliance framework creation service

See merge request gitlab-org/gitlab!47909

Remove use of present tense in ci docs (part 3)

See merge request gitlab-org/gitlab!47995

Part three of a ci doc cleanup

Documentation: Update the doc to include push rules in exports

See merge request gitlab-org/gitlab!47981

Replace fa-chevron-down in template selector dropdown

See merge request gitlab-org/gitlab!48015

Fix kwargs deprecation warnings in project MR resolver specs

See merge request gitlab-org/gitlab!47789

Fix project description schema type

See merge request gitlab-org/gitlab!48038

Update Gitaly reference architectures based on 2K

See merge request gitlab-org/gitlab!47308

Take the recent changes to the Configure Gitaly section of the 2K users
reference architecture page
(https://gitlab.com/gitlab-org/gitlab/-/merge_requests/40875), and
update the remainder of the relevant pages.

Remove use of present tense in ci docs (part 2)

See merge request gitlab-org/gitlab!47987

Part two of a ci doc cleanup

Add a dry-run mode for rack attack

See merge request gitlab-org/gitlab!47545

Geo: Add verification state machine

See merge request gitlab-org/gitlab!47260

Remove use of present tense in ci docs (part 1)

See merge request gitlab-org/gitlab!47983

Part one of a ci doc cleanup

Edit API landing page

See merge request gitlab-org/gitlab!47989

Remove future tense from Gitaly documentation

See merge request gitlab-org/gitlab!47982

Also update link that changed.

Adds a new service:

ComplianceManagement::Frameworks::CreateService to
GitLab EE.

Fix future tense issues in Monitor docset

See merge request gitlab-org/gitlab!48036

This merge request begins to tackle the future-tense issues in the
Monitor documentation. It doesn't completely clean out all instances,
but it contains changes to enough pages that it's time to push the
work into an MR to avoid merge conflicts.

Fix more future-tense issues in Monitor docs

See merge request gitlab-org/gitlab!48037

Update build logs blueprint with status and new PM DRI

See merge request gitlab-org/gitlab!47922

Add "skipped" status to deployments

See merge request gitlab-org/gitlab!46614