Access restrictions for project /google_cloud

See merge request gitlab-org/gitlab!73569

Rename all temporary tables to be prefixed with `_test`

See merge request gitlab-org/gitlab!73824

Fixes blob counts of images on dependency proxy

See merge request gitlab-org/gitlab!73654

Document authorizing projects for an Agent

See merge request gitlab-org/gitlab!73229

Move the cleanup policies cache object

See merge request gitlab-org/gitlab!71584

Updating ipynbdiff to 0.3.7

See merge request gitlab-org/gitlab!73760

Build the Redis::Store instance and use it in session_store

See merge request gitlab-org/gitlab!73552

Enable workhorse_use_sidechannel by default

See merge request gitlab-org/gitlab!73536

Improve ConfigurationPageLayout UX

See merge request gitlab-org/gitlab!73071

In number of places we create temporary tables. This renames
these temporary tables to be prefixed with `_test_`
to exempt them from schema validation.

- Add specs and ENV variable

New project button is blue, not green

See merge request gitlab-org/gitlab!73807

ci: Update GitLab Helm chart version to 5.4.1

See merge request gitlab-org/gitlab!73570

Remove runners' table jobs and projects columns

See merge request gitlab-org/gitlab!73472

Jira Connect: consolidate sign in link update logic

See merge request gitlab-org/gitlab!73813

This updates the developer documentation to reflect the fact that we
stopped using CI_PRE_CLONE_SCRIPT to make the gitlab-org/gitlab CI Git
fetch workload manageable.

This changes the workhorse_use_sidechannel feature flag to be on by
default. This is a performance improvement for Git fetch traffic, see
https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/463.

For self-managed installations that have configured a gRPC proxy to
sit between Workhorse and Gitaly, this will break things. The solution
for that is to remove the proxy or change it to a TCP proxy. Having a
proxy between Workhorse and Gitaly is not a recommended configuration
but we cannot rule out that someone chose to do this. Also see
https://gitlab.com/gitlab-com/gl-infra/scalability/-/issues/1301.

This commit intentionally leaves the feature flag around so that in
case someone runs into this problem, they have a temporary workaround
(disabling the feature flag) besides the real solution (not using a
gRPC proxy).

Changelog: performance

Merge branch '336665-feature-flag-rollout-of-add_actor_based_user_to_snowplow_tracking' into 'master'

[Feature flag] Rollout of: `add_actor_based_user_to_snowplow_tracking` and `add_namespace_and_project_to_snowplow_tracking`

See merge request gitlab-org/gitlab!73677

Added Related topics

See merge request gitlab-org/gitlab!73579

Update Gitaly version

See merge request gitlab-org/gitlab!73816

Replace calls to writeQuery for client mutations in PA

See merge request gitlab-org/gitlab!73682

Merge branch '343510-allow-mr-author-to-automatically-run-review-app-pipeline-by-using-a-label' into 'master'

ci: Allow to force Review App to be deployed with a label

See merge request gitlab-org/gitlab!73568

Updated secrets keyword to meet standards

See merge request gitlab-org/gitlab!73798

Do not run rerun jobs for security project

See merge request gitlab-org/gitlab!73777

We have logic that adds a `return_to` parameter
to sign-in links in the JIra Connect app. This code
was previously duplicated.

This commit consolidates the code into a single helper
function.

There are no user facing changes.

Use allowlist of allowed attributes for imported models (part 5)

See merge request gitlab-org/gitlab!71867

Runner status cannot be "paused" [RUN-AS-IF-FOSS]

See merge request gitlab-org/gitlab!73530

Allow percentage rollout of load balancer of decomposed database

See merge request gitlab-org/gitlab!73631