Merge branch '229912-deploy-freeze-jest-specs-failing-spec-frontend-deploy_freeze-components' into 'master'

Resolve "Deploy freeze jest specs failing: spec/frontend/deploy_freeze/components/deploy_freeze_modal_spec.js"

Closes #229912

See merge request gitlab-org/gitlab!37233

Geo: Fix package file backfill with sync object storage disabled

See merge request gitlab-org/gitlab!36771

Improve docs around `environment:action`

Closes #229140

See merge request gitlab-org/gitlab!37196

Fix enforce_pat_expiration feature flag in docs

See merge request gitlab-org/gitlab!37071

Add example to the multi-version-compatibility

See merge request gitlab-org/gitlab!37031

Fix for link and note in secure clusters doc

See merge request gitlab-org/gitlab!37138

Add graceful timeout handling for analytics

Closes #225405

See merge request gitlab-org/gitlab!36811

Update links to feature flags howto

See merge request gitlab-org/gitlab!37168

Bug Fix: Child pipelines are not found by API endpoints

See merge request gitlab-org/gitlab!36494

Bug Fix: Child pipelines are not found by API endpoint

Resolve "Docs: Set a deploy freeze in the UI"

See merge request gitlab-org/gitlab!36998

Clarify merge train todo behavior

See merge request gitlab-org/gitlab!37220

Fix displaying roadmap for epics without dates

See merge request gitlab-org/gitlab!37093

Log more information about the inbox while waiting

See merge request gitlab-org/gitlab!37202

Remove store singleton pattern from docs

See merge request gitlab-org/gitlab!36952

- Don't document using `Vue.use(Vuex)` in store entry points (this harms
  testability)
- Add note about RFC to prefer named exports
- Don't document passing a store singleton to a component definition;
  this isn't what we do. Instead, just rely on a store being provided by
  an ancestor.
- Using `@vue/test-utils` for component test
- Document `localVue` usage

Geo - Clean up old node css

Closes #229351

See merge request gitlab-org/gitlab!37115

Replaces custom sass file with gitlab-ui
utility classes

Limit project moved e-mails to maintainers/owners

See merge request gitlab-org/gitlab!36665

Previously the "Project was moved" email notifications were sent every
member in the project. This served a useful purpose when we did not have
project redirects, so there was no way to discover that a project had
actually moved. However, these e-mails generate a significant amount of
noise, especially with projects with large number of team members.

To cut down on these notifications, we restrict the e-mails to
project/group maintainers and owners. Later we can introduce custom
notification settings to disable this.

Part of https://gitlab.com/gitlab-org/gitlab/-/issues/30371

Resolve "Set a deploy freeze in the UI"

Closes #24295

See merge request gitlab-org/gitlab!35163

This reverts commit 158003eb65edafd48a814928ddbce56f2a15d8b8.

Rename snippet GraphQL files field to blob_actions

See merge request gitlab-org/gitlab!36852

Add Vuex Store for Allowing Users to Edit User Lists

See merge request gitlab-org/gitlab!37006

This will be used later to allow users to edit the name of an user list.

Add version to group LDAP lock functionality

See merge request gitlab-org/gitlab!37144

Docs: Re-added group runners

See merge request gitlab-org/gitlab!37218

Update dependency @gitlab/ui to v17.34.0

See merge request gitlab-org/gitlab!37167

Related to: https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/52658\#note_381413008

Restore 13.1.0 EE changelog

See merge request gitlab-org/gitlab!37214

Allow refresh rate feature to be disabled via a feature flag

See merge request gitlab-org/gitlab!37195

We should allow refresh rate feature to be disabled via feature flag.

Enabling refresh rate for all user might have impact in performance if
too many of them enable it. We want to release this feature and monitor
it's behavior.