This MR makes it possible to parse an attachment tag on a JUnit report.
It creates a new attachment attribute on a test case object.

Fix inconsistent inflection of Ldap module

See merge request gitlab-org/gitlab!26630

Update deprecated link in documentation

See merge request gitlab-org/gitlab!27091

Support async loading & search of projects

See merge request gitlab-org/gitlab!26661

Fix evidence SHA clipboard hover text

Closes #209002

See merge request gitlab-org/gitlab!26608

Match Monaco's white theme closely with the Pygments theme

See merge request gitlab-org/gitlab!25966

Delete unused CI helper functions

See merge request gitlab-org/gitlab!26999

Deduplicate state properties

See merge request gitlab-org/gitlab!26117

The following state properties have been deduplicated in the
vulnerabilities and security_reports store modules:

- isCreatingNewIssue/isCreatingIssue
- isDismissingVulnerability
- isCreatingMergeRequest

They will now only be set in the root state and not in the modal's
state

Run QA frontend jobs when dependencies are updated

See merge request gitlab-org/gitlab!26837

The QA jobs purpose is to catch if we utilize JavaScript that cannot be
executed on one of the node LTS versions we support for from-source
builds.

Currently we execute the QA jobs on master.

1. This means that they are executed unnecessarily, e.g. on docs only
   branches.
2. The thing which breaks the QA jobs are likely dependency updates, as
   we just test the webpack compilation and dependencies and
   subdependencies are usually requiring newer node versions. So we
   should be executing these checks on branches that update
   dependencies.

Recently we had a red master, because one dependency update required a
newer node version and the pipeline was green [0], [1].

Therefore I am proposing that we run the QA frontend jobs in merge
requests which are changing our package.json or yarn.lock file, as we
want to know if a dependency update would fail our build _before_ a red
master happens.

[0]: https://gitlab.com/gitlab-org/gitlab/-/issues/202187
[1]: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/24413

Extract AdvancedStageWorker to be reused

See merge request gitlab-org/gitlab!26724

Stop using Gitlab::Shell#create_repository in specs

See merge request gitlab-org/gitlab!27009

Add Version and Strategies to FF Edit State

See merge request gitlab-org/gitlab!26895

Expose assets filepath URL on UI

See merge request gitlab-org/gitlab!25635

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

See merge request https://gitlab.com/gitlab-org/gitlab/issues/27300

Update Geo Empty State SVG

Closes #208706

See merge request gitlab-org/gitlab!26325

Replaces underscore with lodash and vanilla JS

See merge request gitlab-org/gitlab!26517

Remove snippet double sync after git action post receive

See merge request gitlab-org/gitlab!27085

The "Important notes about merge requests from forked projects" docs
had an outdated link and it was difficult to find the correct link.
This updates the docs with the correct link.

Add Projects Pipelines Controller Spec

See merge request gitlab-org/gitlab!26844

Comment implementation code and new spec

Render special references for release entities

See merge request gitlab-org/gitlab!26554

This method is going away, and its use in specs hinders that effort.
In specs, it is used to set up scenarios where a repository conflicts
with an attempt to create one, so going through a ::Repository is
typically not an option. We can use `TestEnv#create_bare_repository`
instead, though.

Migrate merge requests mentions to DB table

Closes #198338

See merge request gitlab-org/gitlab!25826

Resolve "code Snippets Description: Markdown is not rendered (it's just plain text)"

Closes #209995

See merge request gitlab-org/gitlab!27038

Use multiple values in list-type CI variable spec

See merge request gitlab-org/gitlab!27031

Fix create issue error by providing the missing param

Closes #209894

See merge request gitlab-org/gitlab!27075

Add support asynchronous search of projects within
dropdown while creating Issue from Epics Tree.

Load derailed_benchmarks fork with Zeitwerk fix

See merge request gitlab-org/gitlab!27080

AdvanceStageWorker is a worker that initally was
used by github importer.

Extracted its functionality so that it can be used by
any multi stage importer to wait for a number of jobs
to complete, without blocking a thread. Once all jobs
have been completed this worker will advance the import
process to the next stage.

Fix two flaky specs that didn't wait for the MR widget to load

Closes #208123

See merge request gitlab-org/gitlab!27078

Expose user's plan and trial status via API

Closes #198391

See merge request gitlab-org/gitlab!25151

`plan` is hooked up to the models but trial is not yet.

Fix spec failures due to PG::LockNotAvailable errors

Closes #207088

See merge request gitlab-org/gitlab!27060

We were seeing a high number of transient failures in the migration jobs
because `with_lock_retries` leaked non-zero, short `lock_timeout` values
(e.g. 100 ms) when used inside a Rails `change` method. If the
PostgreSQL autovacuum process happened to be running, it would lock the
table that it was vacuuming. During the migration rollback, if the DDL
operation needed a lock on the table, the short `lock_timeout` would
encounter the existing table lock and fail.

Even though `SET LOCAL` was used to ensure `lock_timeout` didn't leak
outside of the current transaction, the parent transaction would still
retain that value.

To avoid this issue, we should define separate `up` and `down` methods
so that we don't rely on the Rails magic to reverse a migration. This
ensures lock retries are used properly in both directions and prevents
`lock_timeout` from leaking during a migration rollback.

Closes https://gitlab.com/gitlab-org/gitlab/-/issues/207088

Resolve "Status Page MVC: JSON format and endpoints"

Closes #207935

See merge request gitlab-org/gitlab!26979