Merge branch '12417-add-messages-to-warn-and-stop-users-when-attempting-to-change-the-path-of-projects-with-npm-packages' into 'master'

Resolve "Add messages to warn and stop users when attempting to change the path of projects with NPM packages"

See merge request gitlab-org/gitlab!18515

Log when a pipeline creation limit is hit

See merge request gitlab-org/gitlab!19155

Use existing Sentry exception logging for all
existing limits

Created a constant for archive formats

Closes #35231

See merge request gitlab-org/gitlab!19353

Refactor Pods Logs to Vue in operations/environments

Closes #33537

See merge request gitlab-org/gitlab!18567

- Add new logs component
- Add scroll controls
- Uses backoff for requests to retry
- Makes use of vuex
- Files are present in ee/
- Added specs
- Swtch between new and old component

Use the 'v2.4.4' charts version for Review Apps

See merge request gitlab-org/gitlab!19394

Wait for maven to finish deploying during test

See merge request gitlab-org/gitlab!19413

Use Rails 5.2 Redis caching store

See merge request gitlab-org/gitlab!19202

Allow user to revert back to non-ElasticSearch search

See merge request gitlab-org/gitlab!19136

Docs: update Pages documentation

See merge request gitlab-org/gitlab!19436

- Move getting started content to own docs
- Simplify index's getting started
- Move access control to its own doc
- Rewording for clarity
- Remove redundancies

Embedding Grafana metrics panels in GFM

See merge request gitlab-org/gitlab!18285

Adds filters for supporting the ability to embed Grafana metrics
in GitLab Flavored Markdown. Adds a filter which identifies
references in GFM to the domain corresponding to a configured
GrafanaIntegration for the project.

Note: This is only available for Prometheus datasources which are
configured to be proxied through Grafana.

Better document how to enable Auto Monitoring

Closes #31709

See merge request gitlab-org/gitlab!18949

- Mention the GitLab managed apps in the requirements of Auto DevOps
- Move the applications info in one place
- Be explicit what needs to be done to get Auto Monitoring working

Fix broken formatting of notification buttons

Closes #31893

See merge request gitlab-org/gitlab!16672

Backfill GraphQL field descriptions - part 1

See merge request gitlab-org/gitlab!19233

- Some use API docs copy-pasted material (a smell)
- Some are really obvious (e.g. "user's name"
- Some use labels from the UI

Resolve "Rename cluster_metrics_new.yml"

Closes #14740

See merge request gitlab-org/gitlab!19243

Fix 404 for usage question mark link

See merge request gitlab-org/gitlab!19340

Migrate pipelines specs to Jest & VTU

See merge request gitlab-org/gitlab!19270

Improve frontend codeowners and roulette for Eng. productivity

See merge request gitlab-org/gitlab!19076

Reduce redundancy and move source/target branch selectors to top of MR view

See merge request gitlab-org/gitlab!17559

These sizes come from this design doc:

https://gitlab-org.gitlab.io/gitlab-design/hosted/design-gitlab-specs/
forms-spec-previews/

Presumably, these sizes will be *fairly* standardized so that they
don't mean different things in different places.

Fix `project_tree_restorer_spec` flakiness

Closes #35323

See merge request gitlab-org/gitlab!19427

Revamp Merge Request documentation

See merge request gitlab-org/gitlab!18644

Fixed a typo in the "Keyboard Shortcuts" pop-up

See merge request gitlab-org/gitlab!19217

Migrate issue boards specs to Jest & VTU

See merge request gitlab-org/gitlab!19265

Expand sections by default

Closes #35176

See merge request gitlab-org/gitlab!19320

NPM packages presence is checked before these actions:
* group at the root namespace has a path update
* subgroup is transfered to a different root namespace
* project is transfered to a different root namespace

Fix old content and improve structure, and remove
repetition. Also brings back content deleted by accident

Fail if a test leaves the browser logged in

See merge request gitlab-org/gitlab!18978

All QA tests expect to be able to log in at the start of the test.

That's not possible if a test leaves the browser logged in when it
finishes. Normally this isn't a problem because Capybara resets the
session after each test. But it does that in an `after` block, so when
a test, like this one, logs in in an `after(:all) block, the browser
returns to a logged in state *after* Capybara has logged it out. And
then the next test will fail.

E.g.: https://gitlab.com/gitlab-org/gitlab/issues/34736

This adds a `config.after(:context)` block to fail if a test
leaves the browser logged in.

Improve the only/except extendable jobs

See merge request gitlab-org/gitlab!17956

Move several features from create MR doc to
review MR doc. Also splits security reports into
it's own section, to allow for one ULTIMATE badge

Notice about missing support for Auto Test when using .buildpacks file

See merge request gitlab-org/gitlab!6930

The test builds a maven package in a docker container. The build
process can take a very different amount of time depending on how
long it takes to download all the dependencies and build.

There is an issue open to improve the test, but for now we make it
wait up to 5 minutes to build and deploy. We stop the container as
soon as deployment is complete so that it doesn't wait the full 5
minutes.

We also force delete the temp directory used to store the source for
the package because it seems to take some time for docker to release
the files after the container is stopped.