In order to determine which blobs are new based on a given revision, we
call Gitaly's `ListNewBlobs` RPC. This RPC is rather inflexible though:
it only allows passing a single new revision. As a result, we cannot
batch computation of new blobs across a set changes in our access
checks.

As a first step towards fixing this limitation, we now migrate
`#new_blobs()` to use the `ListBlobs` RPC: this is a much more flexible
variant of `ListNewBlobs`, and most importantly it allows us to pass a
set of revisions. When the old implementation is removed, we can thus
easily allow `#new_blobs()` to receive multiple revisions.

Note that this changes the return type of `#new_blobs()`: instead of
returning a set of `Gitaly::NewBlobObject` classes, we now return a set
of `Gitlab::Git::Blobs`. While both share the same `size` and `path`
attributes, the former tracks the blob ID via an `id` attribute while
the latter uses an `oid` attribute. There is only a single callsite of
`#new_blobs()` though, which is the FileSizeCheck push rule, and this
callsite only uses the `size` and `path` attributes. So in the end, this
change in behaviour is fine.

By default, the ListBlobs RPC will not return file paths of returned
blobs, but we need them when listing new blobs via ListBlobs such that
we can tell users exactly which file is too big in our push rules.

Expose a new `with_paths` parameter, which cause us to request blob
paths from Gitaly.

Upgrade Gitaly's protobuf definitions to v14.3.0-rc1. Amongst other
changes, this also includes the new `with_paths` field in the ListBlobs
RPC call.

Add configure integrations button to project view

See merge request gitlab-org/gitlab!67536

Disable cross-database query check due to frequent segfaults

See merge request gitlab-org/gitlab!69184

Add LRU-like behaviour to incremental compilation

See merge request gitlab-org/gitlab!68956

Use linear version of User#membership_groups

See merge request gitlab-org/gitlab!68842

Update Project URL dropdown on New Project page

See merge request gitlab-org/gitlab!68778

[RUN AS-IF-FOSS] Revert merge requests realted to saas_user_caps feature flag

See merge request gitlab-org/gitlab!69183

Only show tooltip on truncate for commit info

See merge request gitlab-org/gitlab!68889

The use of PgQuery.parse(sql) is causing segfaults so we will disable
this for now

This reverts commit b50ffcb5, reversing
changes made to c33e60d9.

This reverts commit bb456c97.

Add notes on using correlation ids from API

See merge request gitlab-org/gitlab!69176

Fix epic swimlanes list repositioning not working

See merge request gitlab-org/gitlab!68908

Update Version History of Project Security Dashboard to fit its tier

See merge request gitlab-org/gitlab!68694

Only set User#commit_email with user input

See merge request gitlab-org/gitlab!68591

Review X509 page for CTRT purposes

See merge request gitlab-org/gitlab!68792

Add crosslinks to several more permissions

See merge request gitlab-org/gitlab!68816

Sync update of title and description between RequirementsManagment::Requirement objects and requirement type issues

See merge request gitlab-org/gitlab!64929

Between Requirements and Requirement Issues

Wrap updates in pseudo-transaction
Add validation flags when mirrored object
not valid

Changelog: added
EE: true

Docs: improve CI examples page

See merge request gitlab-org/gitlab!69155

Add documentation for gitlab-runner issue 1042

See merge request gitlab-org/gitlab!57354

Revert "Merge branch 'stuck-ci-jobs-worker-optimize-running' into 'master'"

See merge request gitlab-org/gitlab!69163

This reverts merge request !68891

Changelog: other

Optimize StuckCiJobsWorker running builds query

See merge request gitlab-org/gitlab!68891

Render audio in content editor

See merge request gitlab-org/gitlab!68598

Update dependency @gitlab/ui to v32.4.0

See merge request gitlab-org/gitlab!69130

Patch `grape-entity` to prevent having NameError loop

See merge request gitlab-org/gitlab!69040

RubyVM starts raising unlimited amount of `NameError` errors in case of
a `NameError` in our Grape::Entity instances because of a bug exists in
the `grape-entity` gem.

This causes high CPU usage and puts us at the risk of having DoS.
The VM would eventually raise a `SystemStackError` but this takes quite
long time because the repeating frames are huge.

You can track the progress of upstream fix here:
https://github.com/ruby-grape/grape-entity/pull/355

Changelog: fixed

Store fetched group labels in vuex

See merge request gitlab-org/gitlab!64273

Observe duration of each pipeline creation step

See merge request gitlab-org/gitlab!68485

Steal pending merge request diff commit user jobs

See merge request gitlab-org/gitlab!68769