Introduce project_settings table

See merge request gitlab-org/gitlab!19761

Don't render mermaid diagrams in search result

Closes #35962

See merge request gitlab-org/gitlab!23033

Support for table of contents (TOC) in markdown files and issue / MR descriptions

Closes #21901

See merge request gitlab-org/gitlab!24196

`[[_TOC_]]` now gets converted for normal GDM markdown

Resolve "Credentials inventory for group managed accounts"

Closes #38133

See merge request gitlab-org/gitlab!23944

Ignore file_type in Packages::PackageFile

See merge request gitlab-org/gitlab!24534

Run quarantine and pg10 for code changes only on master

Closes #204641

See merge request gitlab-org/gitlab!24766

Blob viewer switcher

See merge request gitlab-org/gitlab!24374

Whenever a blob has richViewer available, the switcher will be shown
to switch between the simple and rich viewers

3/4 components constituting the Blob File header component

Fix service desk settings not showing saved Email Display Name

See merge request gitlab-org/gitlab!24681

Singular is more appropriate and prefixing with project again makes it
more meaningful.

There is no usable data in this table yet, but with this change the
table is created, it's backfilled for every existing project, and new
rows are created as new projects are created. When the background
migration is complete it should be fairly easy to add columns to this
table and store project settings data in this table instead of in the
projects table itself.

This is a first step toward:
https://gitlab.com/gitlab-org/gitlab/issues/19826

Remove full page refresh when ignoring/resolving errors in Sentry

See merge request gitlab-org/gitlab!24542

Upgrade Gitaly to v1.86.0

Closes #27828

See merge request gitlab-org/gitlab!24610

Remove core-js stable import

See merge request gitlab-org/gitlab!24529

This change introduces Introduce Credentials Inventory
at the Group level for Groups that enforce Group Managed Accounts

Convert underscore to lodash for error tracking settings

See merge request gitlab-org/gitlab!24653

Fix GraphQL console warnings when uploading a design

Closes #202292

See merge request gitlab-org/gitlab!24657

Merge branch '37725-pipeline-junit-view-performance-on-running-on-big-data-set-load-async' into 'master'

Load test badge counter asynchronously

See merge request gitlab-org/gitlab!24522

Because we need to fix broken master first. It was broken on master
when there's only docs changes.

Remove addMultipleIssues function logic from list model

See merge request gitlab-org/gitlab!21404

Move some board tests to jest

See merge request gitlab-org/gitlab!24365

Resolve "Abstract common fragments to GraphQL shared folder"

Closes #202228

See merge request gitlab-org/gitlab!24580

Record audit event when user is deleted

See merge request gitlab-org/gitlab!24257

Merge branch '197369-group-and-instance-security-dashboards-hit-the-vulnerabilities-summary-endpoint-without' into 'master'

Skip summary endpoint for Group and Instance Security Dashboard

See merge request gitlab-org/gitlab!23757

The Group and Instance Security Dashboards hit the vulnerability
summary endpoint, even though they're not using the data from it

Frontend: Remove confidence from security reports

See merge request gitlab-org/gitlab!24033

Application limit for ES indexed field length

See merge request gitlab-org/gitlab!24345

There is an edge case when the parent `execute` fails and returns a user
with errors. This should be excluded from audit event logging.

When user is the sole owner of the group no explicit delete
options are enabled, the method is expected to return the
attempted delete user with error messages attached.

The test is to ensure we honour this interface and does not
cause unexpected failures from the callers.

Add version badge for Service Desk feature

See merge request gitlab-org/gitlab!24753

Using the plan_limit table we can down store a limit for the maximum
size of any fields being indexed in Elasticsearch. This is for
https://gitlab.com/gitlab-org/gitlab/issues/201826 . Any strings above
the length limit will be truncated down to the limit.

We default to 0 which means unlimited so this has no affect for
self-managed customers. On GitLab.com we will likely want to set this to
around 20k as a sensible upper limit on what we should store.

Add grammar linting tests for Latin phrases in docs

Closes #199110

See merge request gitlab-org/gitlab!23798