Introduce remediation entity

See merge request gitlab-org/gitlab!47166

- Add the Vulnerability::Remediation model to store remediation
  data in a structured way
- Add the pivot model Vulnerability::FindingRemediation to establish
  many to many relationship between finding and remediation entities
- Add database migrations to create remediation related tables

Update ci yaml ref to remove allows

See merge request gitlab-org/gitlab!48009

We should only use the word allows when talking
about permissions.

e2e: Raise an error if the API response doesn't have the expected field

See merge request gitlab-org/gitlab!48039

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

Schedule CreateEvidenceWorker jobs in a sliding window

See merge request gitlab-org/gitlab!47638

Additional CSS Loading for 3 more Select2 Usages

See merge request gitlab-org/gitlab!48053

Removed unnecessary eslint exception

Replace prepend-left-20 in admin/hooks

See merge request gitlab-org/gitlab!47951

Test(DevOps Adoption): `groups` local resolver

See merge request gitlab-org/gitlab!47793

Improve the tests for the `groups` local resolver
in the Admin/DevOps Adoption tab.

This should serve as a good example to how to test
local resolvers for GraphQL going forward

Document enhancements to MR Analytics

See merge request gitlab-org/gitlab!48046

Recently there were multiple enhancements to the MR Analytics feature:
date range customization, deep linking, pagination and displaying
approval count. This adds documentation for all of these enhancements.

Remove un-used endpoint for embeddable Insights

See merge request gitlab-org/gitlab!47583

A few months ago there was interest in enhancing the Insights feature
to allow for these custom charts to be embedded in other contexts. As
a first step toward that, an endpoint was introduced for these
embeddable charts. However, it has been decided we have higher-priority
features to pursue. So this removes that endpoint code, however we
may choose to restore it in the future if we decide to pursue
embeddable Insights in the future.

Document dependency path for Yarn 1.x

See merge request gitlab-org/gitlab!47931

Update docs for dropping legacy in-cluster PostgreSQL installation

See merge request gitlab-org/gitlab!47874

Update Gitaly version

See merge request gitlab-org/gitlab!48057

Migrate awards list buttons to new buttons

See merge request gitlab-org/gitlab!43061

Fix tests affected by changes

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