Before transfering a group, it's checked if there is already Namespace
with the same path. Currently this effectively checks only if there is a
subgroup with the same path. If there is a project with the same path,
transfer fails too, but in the next step because updated group
validation fails with error `"Validation failed: Group URL has already
been taken"`.

When we create/backfill project namespace for each project, we will
effectively check both for subgroup or project path conflicts (because
project namespace will be created with the same path as project). So we
can just update the error message to mention that there is either group
or project with the same path.

Add mentions of the new . shortcut

See merge request gitlab-org/gitlab!72621

Update CODEOWNERS with workspace and add fneill

See merge request gitlab-org/gitlab!72783

Define SLI before using it in the Rails request apdex SLI docs

See merge request gitlab-org/gitlab!72844

Fixed broken external links

See merge request gitlab-org/gitlab!72471

Guard against missing namespace_settings

See merge request gitlab-org/gitlab!72785

Use disable join to avoid  doing cross-join via `ci_builds` in `Security::Finding.build`

See merge request gitlab-org/gitlab!72738

Ensure regular migrations are permitted

See merge request gitlab-org/gitlab!72558

Make cross-db modification check use running spec

See merge request gitlab-org/gitlab!72735

Update doc remove extra word

See merge request gitlab-org/gitlab!71880

Document tips for use of the Secure scanning tool templates

See merge request gitlab-org/gitlab!72267

Doc Consistency: user/application_security - static analysis

See merge request gitlab-org/gitlab!72644

Doc Consistency: user/application_security - threat insights

See merge request gitlab-org/gitlab!72645

Update audit events documentation screenshot

See merge request gitlab-org/gitlab!72760

E2E: Update selenium to version 4

See merge request gitlab-org/gitlab!72636

Doc Consistency: user/application_security - composition analysis

See merge request gitlab-org/gitlab!72642

Move Agent usage metrics to Core

See merge request gitlab-org/gitlab!72086

Change enforcement label to status

See merge request gitlab-org/gitlab!72394

This makes it consistent with the cross-db query check. Also it's
clearer to use the running spec, instead of the file where the example
is defined

Quarantines flaky VSA metrics tests

See merge request gitlab-org/gitlab!72840

Ignore unimportant StatusSyncError message

See merge request gitlab-org/gitlab!72746

Major CTRT revision of mirroring page

See merge request gitlab-org/gitlab!71140

Remove the rails_request_apdex_counters feature flag

See merge request gitlab-org/gitlab!72427

- move i18n strings out of vue template

- enforcement is unnecessary

Changelog: changed
EE: true

Fix File resource web_url property

See merge request gitlab-org/gitlab!72712

Doc Consistency: user/application_security - dynamic analysis

See merge request gitlab-org/gitlab!72640

Documentation: Fix/Prettify kankiko example

See merge request gitlab-org/gitlab!72286

Revert "Merge branch 'pks-ci-use-gitaly-git' into 'master'"

See merge request gitlab-org/gitlab!72828

Related to https://gitlab.com/gitlab-org/gitlab/-/issues/338332
this MR quarantines the offending tests.