Speed up avatar URLs with object storage

Closes #43065

See merge request gitlab-org/gitlab-ce!26858

Add v2 to reserved top level routes

See merge request gitlab-org/gitlab-ce!26540

GraphQL Type authorization

Closes #54417

See merge request gitlab-org/gitlab-ce!25724

Add testing to feature proposal template

See merge request gitlab-org/gitlab-ce!26779

Filters branch and path labels for metrics

Closes #48090

See merge request gitlab-org/gitlab-ce!26744

With object storage enabled, calling `#filename` on an upload does this:

1. Call the `#filename` method on the CarrierWave object.
2. Generate the URL for that object.
3. If the uploader isn't public, do so by generating an authenticated
   URL, including signing that request.

That's all correct behaviour, but for the case where we use `#filename`,
it's typically to generate a GitLab URL. That URL doesn't need to be
signed because we do our own auth.

Signing the URLs can be very expensive, especially in batch (say, we
need to get the avatar URLs for 150 users in one request). It's all
unnecessary work. If we used the `RecordsUploads` concern, we have
already recorded a `path` in the database. That `path` is actually
generated from CarrierWave's `#filename` at upload time, so we don't
need to recompute it - we can just use it and strip off the prefix if
it's available.

On a sample users autocomplete URL, at least 10% of the time before this
change went to signing URLs. After this change, we spend no time in URL
signing, and still get the correct results.

Move tag quick action spec to shared example

Closes #59570

See merge request gitlab-org/gitlab-ce!26904

Extract merge quick action to a shared example

Closes #59570

See merge request gitlab-org/gitlab-ce!26925

Work around lack of HTML list support in topic

Closes #59338

See merge request gitlab-org/gitlab-ce!26964

Download a folder from repository

Closes #24704

See merge request gitlab-org/gitlab-ce!26532

Merge branch '59979-update-documentation-about-only-allow-merge-requests-to-be-merged-if-the-pipeline-succeeds-to-take-into-account-the-settings-page-reorganization' into 'master'

Update "Pipelines must succeed" documentation

Closes #59979

See merge request gitlab-org/gitlab-ce!26945

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Backport: Use merge request MERGE ref for attached merge request pipelines

See merge request gitlab-org/gitlab-ce!26702

Add pipeline bridge presenter

See merge request gitlab-org/gitlab-ce!26911

Prevent premailer from replacing HTML entities

Closes #55964

See merge request gitlab-org/gitlab-ce!26931

Backport some changes from gitlab-ee!9815

Closes #3314

See merge request gitlab-org/gitlab-ce!25908

Show backtrace when logging to kubernetes.log

Closes #56768

See merge request gitlab-org/gitlab-ce!25726

Expose pipeline in the related merge requests

Closes #57662

See merge request gitlab-org/gitlab-ce!26367

Expose head pipeline for the MR in the api when requesting
related merge requests for an issue and show a detailed
status for the pipeline, which would include:
details_path, favicon, group, icon, label, text, tooltip.

https://gitlab.com/gitlab-org/gitlab-ce/issues/57662#note_152023412

Fix swipe diff divider

Closes #60005

See merge request gitlab-org/gitlab-ce!26970

In the Vue image diff app, the border needs to be on the right because
the new image comes in from the left. The old image diff app which is
used in commits and compare views had the new image visible by default
and hiding away from the left.

Copy sidebar todo component from EE

Closes gitlab-ee#9954

See merge request gitlab-org/gitlab-ce!26915

Deduplicate frontend dependencies

Closes #59878

See merge request gitlab-org/gitlab-ce!26916

Support time window parameters in additional metrics endpoint

See merge request gitlab-org/gitlab-ce!26228

It's duplication information as we already send the full error object to
Sentry.

As it already has the full error sent to it

DRY up tests for logging error.

This prevents `&mdash` in our templates being change to `-`

Just the error message and error class alone makes it hard to determine
the full context of any errors, so we need to know where the error is
occuring as well.

Add docs to `only:changes/except:changes` that discuss using regex in certain scenarios

See merge request gitlab-org/gitlab-ce!26831

Backport changes to CE

Fix broken spec for Merge request > Revert modal

See merge request gitlab-org/gitlab-ce!26961