Remove incorrect localVue usage in ee/spec/frontend/related_items_tree

Closes #121601

See merge request gitlab-org/gitlab!22585

Remove incorrect localVue usage in ee/spec/frontend/geo_designs

Closes #121598

See merge request gitlab-org/gitlab!22588

Remove incorrect localVue usage in ee/spec/frontend/approvals

Closes #121592

See merge request gitlab-org/gitlab!22591

Merge branch '121748-clean-unnecessary-localvue-in-various-standalone-specs-on-spec-frontend' into 'master'

Clean unnecessary 'localVue' in various specs on 'spec/frontend'

See merge request gitlab-org/gitlab!22464

Remove incorrect localVue usage in spec/frontend/diffs

Closes #121741

See merge request gitlab-org/gitlab!22581

Remove incorrect localVue usage in ee/spec/frontend/project_licenses

Closes #121600

See merge request gitlab-org/gitlab!22586

Subscription details component for paid signup flow

See merge request gitlab-org/gitlab!21563

Remove incorrect localVue usage in spec/frontend/monitoring

Closes #121742

See merge request gitlab-org/gitlab!22580

Revert "Merge branch 'create-downstream-pipeline-in-same-project' into 'master'"

See merge request gitlab-org/gitlab!22571

Revert "Merge branch 'add-parent-child-pipeline-limitations' into 'master'"

See merge request gitlab-org/gitlab!22574

localVue is required only with use method

localVue is required only with use method

localVue is required only with use method

localVue is required only with use method

API to create self monitoring project and monitor status

See merge request gitlab-org/gitlab!21428

localVue is required only with use method

localVue is required only with use method

Replace breakpoints with GlBreakpointInstance in contextual_sidebar.js

See merge request gitlab-org/gitlab!22079

This reverts merge request !21817

Add initial limits doc

Closes #35650

See merge request gitlab-org/gitlab!20378

Merge branch '31421-docs-setting-default-expiration-does-not-affect-previously-created-artifacts' into 'master'

docs: setting default expiration does not affect previously-created artifacts

Closes #31421

See merge request gitlab-org/gitlab!22435

Add parent/child pipeline limitations

See merge request gitlab-org/gitlab!21817

Docs: S3 bucket can't include subdirectories

See merge request gitlab-org/gitlab!22268

Refactor DeploymentMetric to reuse code

Closes #119297

See merge request gitlab-org/gitlab!22458

Add API for updating a remote mirror's attributes

Closes #194105

See merge request gitlab-org/gitlab!22433

Add functionality for when user edits max issue count

See merge request gitlab-org/gitlab!21962

On the board setting sidebar, when the sidebar is open
the user can now update wip limits based on max
issue count.

Comments;

Add debug lines on pipeline trigger

See merge request gitlab-org/gitlab!22569

Add CSP headers for Sourcegraph

See merge request gitlab-org/gitlab!20512

This reverts merge request !20930

Fix deploy tokens erroneously triggering unique IP limits

Closes #22854

See merge request gitlab-org/gitlab!22445

Reverts "Add RBAC permissions for getting knative version"

See merge request gitlab-org/gitlab!22560

This reverts commit f0631507.

Also renamed SourcegraphGon to SourcegraphDecorator

**Note:**

- If CSP values are set, it uses the values from
default-src if connect-src is not available. This
way the intention of the CSP config remains intact.

Some users were complaining that when the user unique IP limiter was
enabled, they would be banned for some unknown
reason. `AuthFinder.find_for_git_client` can authenticate users from a
multitude of tokens (CI, LFS, HTTP basic auth, etc.), but project deploy
tokens are unique in that they aren't attributed to a specific user. As
a result, if project deploy tokens were used, users that had the same
database ID as a deploy token would erroneously be attributed to using
the IP accessed by the token.

To fix this issue, we only call `Gitlab::Auth::UniqueIpsLimiter` if a
user is returned from the authentication search. Project deploy tokens
could be used from many different IPs, so it doesn't make sense to group
them with user activity.

Possibly fixes https://gitlab.com/gitlab-org/gitlab/issues/22854

Adds section describing ci_dag_limit_needs usage

See merge request gitlab-org/gitlab!22295