Support Docker OCI images

Closes gitlab-ee#12877 and #58685

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

Vue-i18n: Autofix additional i18n lints for vue files

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

Autofixes additional linting errors
found in vue files.

Autofix i18n lints for vue files

See merge request gitlab-org/gitlab-ee!14837

Refactor usage data counters specs

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

Usage data design management

See merge request gitlab-org/gitlab-ee!14779

This makes these tests available for other implementations

[CE] Create serializer for Jira API JSON payload

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

Create serializer for Jira API JSON payload

See merge request gitlab-org/gitlab-ee!14560

Docker Distribution v2.7.0 shipped with OCI support, but our container
registry client was not updated to handle the manifest format in the
HTTP `Accept` header.  As a result, API calls to retrieve a manifest
would return with an error, "OCI manifest found, but accept header does
not support OCI manifests". This would result in blank fields in the
container registry page and prevent tags from being deleted.

To fix this, we just need to add
`application/vnd.oci.image.manifest.v1+json` to the `Accept` header and
configure Faraday to parse the response as JSON. The response structure
is the same as the standard Docker Distribution V2 manifest.

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/58685

Closes https://gitlab.com/gitlab-org/gitlab-ee/issues/12877

Revert "Workaround for Rails 5, where LIMIT..."

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

Merge branch '12527-comments-in-the-designs-tab-should-support-todo-s-email-notifications' into 'master'

Ensure TO-DO's are applied to comments on designs

Closes #12527

See merge request gitlab-org/gitlab-ee!14804

Return an ETag header for the archive endpoint

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

Grant alert bot reporter access programmatically

See merge request gitlab-org/gitlab-ee!14801

Before this commit the alert bot could not create labels on project
with private issue access ALTHOUGH it has `:reporter_access`.

Reason: In order to check project `issues_disabled` rule we check user's
team access level. AFAIK, there's no way to utilize `:reporter_access`.

Allows the client class to accept a project with commits,
branches, and merge requests and then serializes these
to the JSON format Jira expects

Partial CE-EE parity for specs

See merge request gitlab-org/gitlab-ee!14832

Partial CE-EE parity for specs

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

Make RelativePositioning reusable

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

Make RelativePositioning reusable

See merge request gitlab-org/gitlab-ee!14792

CE port of "Fix spam in issue creation by making project private"

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

Fix spam in issue creation by making project private

Closes gitlab-org/quality/staging#63

See merge request gitlab-org/gitlab-ee!14773

Added an end to end test for the project Security Dashboard

See merge request gitlab-org/gitlab-ee!14654

Adds an additional end-to-end test validating that the results of Secure
  tool scans appear on the Project-level Security Dashboard.
Also fixes a minor issue with the Secure Pipeline reports test
  that created a duplicate job.

Autofixes additional linting errors
found in vue files.

Docs: Improve SCIM documentation

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

Support Feature Flag userWithId Strategy on Backend

See merge request gitlab-org/gitlab-ee!14752

Accept userWithId strategy from frontend
Return strategy to unleash clients
Validate userWithId strategy parameters