For vast majority of these issues, the triage policy automatically adds
the label and no one adds a weight

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.

Update GitLab UI/SVG

See merge request gitlab-org/gitlab!35614

Quarantine Jira issue import e2e spec

See merge request gitlab-org/gitlab!35679

Use snippet `blobs` field instead of `blob` for Snippet VIEW

See merge request gitlab-org/gitlab!35605

Added reference to Kubernetes related deployment variables list

See merge request gitlab-org/gitlab!35506

As per maintainer's review

Fix suggestion dropdown blocking buttons after mention

Closes #225346

See merge request gitlab-org/gitlab!35655

This commit quarantines the flaky test
instance_audit_logs_spec.rb
as tracked at
https://gitlab.com/gitlab-org/gitlab/-/issues/218332

Even if we only support just one blob per
snippet, we're peparing ourselves for the
multi-file scenario in Snippets

In the multi-file scenario for snippets we switch to 'blobs' array
instead of direct 'blob' object

Update toNounSeriesText to not escape text

See merge request gitlab-org/gitlab!35564

Update tests and grammar.js to account for no escaping as well

Move filter code to finder

Closes #31418

See merge request gitlab-org/gitlab!34470

Replace FA exchange icon with GitLab SVG

Closes #225198

See merge request gitlab-org/gitlab!35634