Change CI variable font family to monospace

See merge request gitlab-org/gitlab!34788

Remove "Edit dashboard" button from self monitoring dashboard

See merge request gitlab-org/gitlab!35521

Fix exception handler in changelog Dangerfile

See merge request gitlab-org/gitlab!35656

Add cluster reindexing feature to our ES integration

Closes #213629

See merge request gitlab-org/gitlab!34069

This MR automates steps for the cluster reindexing process
Elastic::ClusterReindexingService is the main class responsible for
the reindexing process

Update deleted and redirected handbook links

See merge request gitlab-org/gitlab!35704

Many handbook pages were changes, redirected, or
deleted. Updates all affected links

Add check for "secrets" runner feature

See merge request gitlab-org/gitlab!34813

Refactor `3_create/gitaly/high_availability_spec.rb` to use `let` syntax

See merge request gitlab-org/gitlab!34222

Use snake_case for metrics data and save them in a fixture

Closes #215316

See merge request gitlab-org/gitlab!33574

Require k8s cluster for DAST template

See merge request gitlab-org/gitlab!35259

During transition to rules syntax, we missed the condition required to
ensure DAST jobs only execute if a cluster is present. Replacing the
previous `only:kubernetes` behavior, we need `CI_KUBERNETES_ACTIVE`

Relates to https://gitlab.com/gitlab-org/gitlab/-/issues/224117

Move cluster_health frontend files to core

See merge request gitlab-org/gitlab!35198

More consistency for Vale style files

See merge request gitlab-org/gitlab!35701

This builds on top of
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/34587 to add check
if "secrets" is feature supported by the runner.

Related to https://gitlab.com/gitlab-org/gitlab/-/issues/28321 and
https://gitlab.com/gitlab-org/gitlab/-/issues/218746.

Clarifying Fast SSH lookup tests, SELinux support

See merge request gitlab-org/gitlab!33470

Remove sentence about the end of /help

See merge request gitlab-org/gitlab!35673

Mark default value for artifacts

See merge request gitlab-org/gitlab!35658

Geo - Does not sync LFS objects from fork networks

Closes #225427

See merge request gitlab-org/gitlab!35692

Add scanner column to the project-level security dashboard and pipeline security tab

See merge request gitlab-org/gitlab!35150

Quarantine instance_audit_logs_spec.rb

See merge request gitlab-org/gitlab!35654

Include snippets_size statistic inside RootStorageStatistics

See merge request gitlab-org/gitlab!35601

Add snippets_size to RootStorageStatisticsType

See merge request gitlab-org/gitlab!35586

Improve package factory to fix spurious spec

See merge request gitlab-org/gitlab!35410

Fix a few package factories which don't
work on their own.

Remove OnBoarding tour - FE

See merge request gitlab-org/gitlab!35442

Add instrumentation to Gitaly streamed responses

See merge request gitlab-org/gitlab!35283

Docs: review add_remove_clusters

Closes gitlab-com/support/support-team-meta#2292

See merge request gitlab-org/gitlab!33311

Merge branch '218794-restructure-documentation-to-consolidate-vulnerability-management-features' into 'master'

Security Dashboard doc improvements

See merge request gitlab-org/gitlab!35558

Added screenshots with nav hidden
Consolidated vuln export report info
Removed out of date and incorrect  info

Docs: shared runner update

See merge request gitlab-org/gitlab!35546

Related to community comment: http://disq.us/p/2a8h51o

This is a stab into fixing the Gitaly timing in logs (gitaly_duration_s)
for streamed responses using the same GitalyClient.call method.

The problem of having a GitalyClient.call for non-streamed responses
and GitalyClient.streaming_call (with a block) for streamed responses
is that we'll need to rely mostly on documentation in order to
get the timings right for new RPCs.

In order to solve that, here we look further into the Gitaly response.
If it's an Enumerator (that's what the Ruby implementation of gRPC
streams return from the server https://grpc.io/docs/languages/ruby/basics/),
we wrap that Enumerator into a custom enumerator, which instruments
that stream consumption.

Another advantage of that over wrapping the whole stream consumption
into a block is that we won't add too much of Ruby CPU time at it,
just the response.next call is measured, which is the point of
contact with Gitaly.