CE-port of 10546-fix-epic-depth-validation

Resolve "Hide Kubernetes cluster warning if project has cluster related"

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

Fix and expand Gitaly FindCommit caching

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

Fix UI anchor links after docs refactor

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

Display cluster form validation error messages inline

Closes #57602

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

Replace comment by variable

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

Instead of having a comment describing what a specific value is,
better to have a variable with a meaningful name.

https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/26248 added
support for deduplicating FindCommit requests using Gitaly ref name
caching. However, not all endpoints were covered, and in one case the
Gitaly wrapper wasn't actually surrounding the serialization step. We
can safely cache ref names between FindCommit calls for #index and #show
endpoints for merge requests and pipelines. This can significantly
reduce the number of FindCommit requests.

Improve the Review Apps documentation by using gitlab-rails console

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

Update gitlab/eslint-config version

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

Drop legacy artifacts usage as there are no leftovers

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

Fix a KeyError in GitlabSchema

Closes #60057

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

Rename Workhorse terminal_specification to channel_specification

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

We're moving from using terminology related to terminals when
we refer to Websockets connections in Workhorse.
It's more appropiate a concept like channel.

Allow reactive caching to be used in services

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

Add support for defining a reactive_cache_worker_finder function
that will be used by the reactive_caching_worker to generate/initialize
the calling object. This allows reactive caching to work with Services
where the object cannot be obtained from DB but a new object can be
initialized.

Allow GraphQL Scalar-fields to be authorized

Closes #57831

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

Externalize strings in helpers

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

- Update qa selector
- Update PO file

Fix vue render error for IDE status bar

Closes #59995

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

Allow to sort wiki pages by date and title

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

- Add controls for sorting by title and date
- Execute Gitaly call which now accepts sorting params for wikis

Update GitLab Shell to v9.0.0

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

Signed-off-by: Rémy Coutable <remy@rymai.me>

Basic limiting complexity of GraphQL queries

Closes #58405

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

Resolve "Automatically set Prometheus step interval"

Closes #58839

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

By computing the step interval passed to the query_range Prometheus API
call we improve the performance on the Prometheus server and GitLab by
reducing the amount of data points sent back and prevent Prometheus
from sending errors when requesting longer intervals.

Resolve "Failing group transfer disables expandable sections"

Closes #45511

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

Extract confidential quick action spec to a shared example

Closes #59570

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

Add a link to S3 Permission Scopes for registry object storage

Closes #58881

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

Allow to use untrusted ruby syntax

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

This brings support for untrusted regexp for 'only:refs:' when
enabled via feature flag: alllow_unsafe_ruby_regexp.

This is by default disabled, and should not be used in production

**What?**

A Vue warning that `ide_status_bar` sent a `Boolean` to a `String`
property (`img-src).

**What was the fix?**

Previously, `latestPipeline` could be one of the following values:

|          |        |
|----------|--------|
| `null`   | The pipeline hasn't loaded yet |
| `false`  | The pipeline has loaded, but nothing was returned. |
| `Object` | The piepline has loaded. |

Giving a semantic meaning to different falsey values hurts
maintainability. This commit fixes the above problem by removing the
`false` value and introducing a `hasLoadedPipeline` state property.