This adds bold and severity-specific colour styling to the numbers of
critical and high severity vulnerabilities in the security-related merge
request widgets.

Addresses https://gitlab.com/gitlab-org/gitlab/-/issues/221084.

Removing unused symbol folder

See merge request gitlab-org/gitlab!36858

Test report link fix

See merge request gitlab-org/gitlab!36220

Rename snippet_files to snippet_actions in snippet services

See merge request gitlab-org/gitlab!36841

Add confidential to graphQL for notes creation

See merge request gitlab-org/gitlab!36799

Add a rule to detect improper alert boxes

See merge request gitlab-org/gitlab!36788

Find and replace all note alert boxes and fix
the colon usage.

Create GitLab issues from PagerDuty webhook payload (Part 1)

See merge request gitlab-org/gitlab!36489

Replace append-right-10 class

See merge request gitlab-org/gitlab!36373

Remove an obsolete TODO comment

See merge request gitlab-org/gitlab!36696

Update to Grape v1.4.0

See merge request gitlab-org/gitlab!36628

Grape v1.4.0 fixes a memory leak that was present in v1.3.3
(https://github.com/ruby-grape/grape/pull/2084).

Full list of changes:

* https://github.com/ruby-grape/grape/blob/master/CHANGELOG.md
* https://github.com/ruby-grape/grape/compare/v1.3.3..v1.4.0

Geo - Make Registry tables as SSOT for Designs

Closes #212720

See merge request gitlab-org/gitlab!36587

Include Elasticsearch query params in Performance Bar

See merge request gitlab-org/gitlab!36899

Check whether PagerDuty setting is active when
creating incident issue

Extract
`Gitlab::IncidentManagement::PagerDuty::IncidentIssueDescription`
from
`IncidentManagement::PagerDuty::CreateIncidentIssueService`

Replace fa-play icon with GitLab SVG play

See merge request gitlab-org/gitlab!36379

- remove css on fa-play class
- replace two fa-play instances

Update metrics dashboard base path

See merge request gitlab-org/gitlab!36749

Replace loading state with an icon, show dashboard skeleton earlier

See merge request gitlab-org/gitlab!36399

Prevent 2nd Elasticsearch query for project searches

See merge request gitlab-org/gitlab!36672

Added option to view diffs file-by-file

See merge request gitlab-org/gitlab!35223

Document new Babel flag

See merge request gitlab-org/gitlab!36671

E2E test delete pipeline via API

See merge request gitlab-org/gitlab!36389

Docs: Simplify `rules` description

See merge request gitlab-org/gitlab!36816

Update Managed Apps Helm version to 2.16.9

See merge request gitlab-org/gitlab!36746

Remove the restriction of trial_end date

See merge request gitlab-org/gitlab!36878

We memoize the result object so that when it is later evaluated the same
Elasticsearch result can be used for the `total_count`.

We also extract a shared test examples for the 3 different kinds of
Elastic search results to reduce the chance of regression here.

This memoize approach to solving this problem was originally introduced
in https://gitlab.com/gitlab-org/gitlab/-/merge_requests/13120

Note that some of the methods being memoized have arguments and as such
the memoization is not logically consistent from the code perspective.
We must memoize the results without the page argument because
the current page we're on - if we were to memoize with dynamic
parameters we would end up hitting ES twice for any page that's not page
1, and that's something we want to avoid.  It is safe to memoize the
page we get here because the method is always called before
the equivalent `#_count` method.

Read more at https://gitlab.com/gitlab-org/gitlab/-/issues/219209

Alert Opsgenie integration

See merge request gitlab-org/gitlab!36199

This is just an MVC and we already know that it's unlikely that
future iterations will be using any of store data.

Therefor, we decided to store the data needed as service properties
and not in a separate database table to avoid churn.