We don't need a repository, and we only need a private user in one
example, so we can scope it locally there.

This will allow us to reuse them in an EE-only spec.

Resolve "table_exists? not compatible with Rails 5.1"

Closes #54478

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

[EE] Resolve "table_exists? not compatible with Rails 5.1"

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

Remove duplicate content about auto-devops customization

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

Update guidance for EE doc submissions

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

Note GitLab University may be out of date in parts

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

Update documentation for current state

Closes #64710

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

Stop printing dots while retrieving pod in review-apps.sh

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

Improve steps for setting commit email

Closes #54881

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

Refine topics for Phase 2 of SSoT audit

Closes #64682

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

Includes admin_area and application_security
topics.

Restructure project cluster topic

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

Also fixes links to section headings that
have changed.

Add a section of examples to code review docs

Closes #64194

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

We have a fairly good guide to Code Reviews, but can be improved
by adding a few examples of what a good code review looks like
at GitLab, specifically ones where there is a bit of back and
forth, "nit-picking," etc. This would:

+ help set expectations of newly hired engineers around what our
process looks like when it is functioning what level of scrutiny
their code will be under

+ how we have technical conversations

+ show by example how after you're done crafting a solution, there
can still be extra work done either tidying up code and/or managing
the communication and conversations about your proposed MR

Fix typo in param name

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

Clarify difference between project name and project path for API usage

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

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