Merge branch '34910-display-security-navigation-in-left-sidebar-to-a-cohort-of-net-new-com-signups' into 'master'

Security navigation in left sidebar

See merge request gitlab-org/gitlab!21658

Merge branch '197497-when-user-clicks-on-exit-while-editing-work-in-progress-limits-user-gets-error' into 'master'

Fix error on close of board sidebar when editing

Closes #197497

See merge request gitlab-org/gitlab!23532

Upgrade @gitlab/svgs to v1.91.0

See merge request gitlab-org/gitlab!23803

Add Group Seeder rake task

See merge request gitlab-org/gitlab!21657

Add screenshot to code review analytics page, small text changes

Closes #198271

See merge request gitlab-org/gitlab!23644

Document self-hosted project webhooks limits

Closes #196018

See merge request gitlab-org/gitlab!23596

Moved the log setup at the bottom

See merge request gitlab-org/gitlab!22916

Add support to seed all package types

See merge request gitlab-org/gitlab!23156

Refactor project destroy services

See merge request gitlab-org/gitlab!22908

In preparation for
https://gitlab.com/gitlab-org/gitlab/merge_requests/22672,
we need to refactor Projects::DestroyService. At the
moment, this service has hardcoded the repositories it
has to delete.

Nevertheless, we have now more requirements that
we had before. We need to remove Snippet repositories
and also DesignManagement ones.

In this commit, we refactor the existing
Projects::DestroyService creating two services just for
dealing with repositories and extracting this
functionality from this service.

We also split some of the existing functionality. The
current destroy service delete things but also is able
to rollback stuff. We can move this functionality into
a different service.

Document troubleshooting when SCIM extern_uid doesn't match SAML NameID

Closes #33378

See merge request gitlab-org/gitlab!19323

Added documentation on how to address error

Closes #195393

See merge request gitlab-org/gitlab!23403

Feature flag: removal of filter_shas_with_signatures_go

See merge request gitlab-org/gitlab!23752

Clarify Kubernetes cluster creation sources

See merge request gitlab-org/gitlab!23638

Trim extra period when merge error displayed

See merge request gitlab-org/gitlab!23737

Revert "Merge branch 'aws-version-bump' into 'master'"

See merge request gitlab-org/gitlab!23829

Gitaly was migrated to Go implementation.
Feature flag is not used anymore.
Please see: https://gitlab.com/gitlab-org/gitaly/-/merge_requests/1703

Part of: https://gitlab.com/gitlab-org/gitaly/issues/2268

Add Epics Activity info to Group Export

Closes #198523

See merge request gitlab-org/gitlab!23613

Updates security release template

See merge request gitlab-org/gitlab!23822

Stop exposing Secure artifacts in MR widget entity

See merge request gitlab-org/gitlab!23824

This reverts merge request !22865

We are not consuming the endpoints anymore, since we are now using the
new comparison endpoints. Thus we can stop exposing them.

After moving the development from dev.gitlab.org to a private group on
gitlab.com/gitlab-org/, we no longer need links on dev. This MR updates
the security release issue template to reflect that.

Drop kibana_hostname column

See merge request gitlab-org/gitlab!23503

Fix Rubocop offenses for cops with 1 or 2 offenses

See merge request gitlab-org/gitlab!23506

Dequarantine clone using deploy key spec

Closes #196047

See merge request gitlab-org/gitlab!23799

Remove open icon from function endpoint

Closes #196855

See merge request gitlab-org/gitlab!23508

Resolve "Knative domain name/endpoint section links to invalid doc"

Closes #38297

See merge request gitlab-org/gitlab!23715

This growth experiment displays the security navigation and a
slideshow of security features to a cohort of net new .com users

Skip squashing with only one commit in a merge request

Closes #198971

See merge request gitlab-org/gitlab!23744

We noticed in https://gitlab.com/gitlab-org/gitaly/issues/2395 that the
backend was unnecessarily attempting to squash merge requests with one
commit. This happened because `SquashService` skips the squash if two
conditions are met:

1. The number of commits < 2
2. The `squash_commit_message` is null

If a `squash_commit_message` is passed, this indicates that the user
wants the squashed commit to have a different commit message.

By default, the frontend always sends `squash_commit_message`,
regardless of whether the squash button is available in the merge
request. With this change, the frontend will only send this parameter if
the button is shown (i.e. when the commit count is >= 2).

Alternatively, we could also change the backend to skip squashing if
only the first condition is met.

Closes https://gitlab.com/gitlab-org/gitlab/issues/198971

Fix error displaying group edit page

See merge request gitlab-org/gitlab!23774

Use CTE optimization fence for loading projects in dashboard

Closes #198440

See merge request gitlab-org/gitlab!23754