Move Settings Operations controller to CE

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

This commit prepares the structure for the upcoming feature error
tracking.

Use BuildMetadata to store build configuration in JSONB form

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

Hide Auto DevOps banner for projects with CI file or CI disabled

Closes #52446

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

Fix multipart attachments not uploading

Closes gitlab-ee#9035

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

Add API Support for Kubernetes integration

Closes #40473

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

Require Knative to be installed only on an RBAC kubernetes cluster

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

Mixing and matching the use of Rack::Request and ActionDispatch::Request
in Rails 5 is bad, particularly if you have middleware that
manipulates or accesses environment variables.

`Gitlab::Middleware::Multipart` attempts to rewrite request parameters
to the proper values (e.g. replacing `data_file` with
`UploadedFile`). It does this by calling `Rack::Request#update_params`,
which essentially updates `env['rack.request.form_hash']`.

By changing to `ActionDispatch::Request`, the Go middleware was causing
the request parameters to be stored inside
`env['action_dispatch.request.request_parameters']`. Later calls to
`Rack::Request#update_params` would not have any effect because it would
attempt to update `env['rack.request.form_has']` instead of
`env['action_dispatch.request.request_parameters']`. As a result, the
controller still saw the old parameters.

Since the Go middleware appears to be using `ActionDispatch::Request`
for authorization methods, we can switch the multipart middleware to
use it too.

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

Fix broken master api_variables test

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

[ci skip]

ADO banner is being hidden if:
- Project has no CI configuration
- Project has CI disabled

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

Merge branch '4553-geo-hashed-storage-migration-failure-does-not-log-to-sentry-or-geo-log-well-ee' into 'master'

Backport of https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/8926

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

Adds the following initial CRUD endpoints for Clusters API:

- GET list of clusters
- GET specific cluster
- POST add existing cluster (mimic of "Add cluster")
- PUT update cluser
- DELETE destroy cluster

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

Support new report syntax for common vulnerabilities (CE backport)

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

Update serverless extension to yml

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

Backport of https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/8926

Fixes broken link

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

Fix deprecation: returning false in Active Record and Active Model callbacks

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

This MR also removes other reports and uses one common set of fixtures
for all test types.

Add project code view permissions

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

Don't ignore conflicts in db/schema.rb

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

Expose `CI_API_V4_URL` CI/CD variable

Closes #54621

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

Improve documentation about only except default values

Closes #55699

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

Include templates

Closes #53445

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

These are data columns that store runtime configuration
of build needed to execute it on runner and within pipeline.

The definition of this data is that once used, and when no longer
needed (due to retry capability) they can be freely removed.

They use `jsonb` on PostgreSQL, and `text` on MySQL (due to lacking
support for json datatype on old enough version).

It's not entirely clear to me why we were ignoring db/schema.rb in the
first place, but this should not be done now that we merge CE into EE
automatically. Doing so can lead to changes being thrown away in the
event of a conflict, which can then lead to EE pipelines failing.

Don't ingore the `gitlab.pot` in ee_compat_check

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

Guarantee visually correct order of runners on the "Admin Area > Runners" page

Closes #49791

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

Documentation for Release page MVC

Closes #41766

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

If there are new strings in CE, they need to be added to EE
manually. As the `locale/gitlab.pot` file can't be merged
automatically during the upstream merge.

This rewrites a syntax to allow include of templates.
This also normalises the syntax used by include: feature

Support asset links creation in `POST /projects/:id/release`

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