Update Gitaly version

See merge request gitlab-org/gitlab!51684

Boards - Get projects on group board using graphQL [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!51291

Split project_select.vue component to create a version using GraphQL

Fix the Maven duplicate setting logic

See merge request gitlab-org/gitlab!51524

When maven_duplicates_allowed is set to false
Maven package files of different formats are still
allowed to be uploaded to an existing package.

Merge branch '297500-flaky-test-spec-features-merge_request-user_closes_reopens_merge_request_state_spec-rb-87' into 'master'

test: Quarantine flaky tests

See merge request gitlab-org/gitlab!51586

Add milestone to null_hypothesis experiment feature flag yaml

See merge request gitlab-org/gitlab!51661

Refactor folder structure for security dashboard GraphQL files

See merge request gitlab-org/gitlab!51117

Enable optional_code_owners_sections by default

See merge request gitlab-org/gitlab!51643

Cases to consider when using feature flags

See merge request gitlab-org/gitlab!50574

Remove unneeded index

See merge request gitlab-org/gitlab!51676

Update repository mirroring UI text

See merge request gitlab-org/gitlab!51311

Update pipeline alert text to be more readable

See merge request gitlab-org/gitlab!49575

Update toast position on set status

See merge request gitlab-org/gitlab!50886

CI: use commit SHA in persistent refspec

See merge request gitlab-org/gitlab!51208

A Git fetch refspec normally looks like 'refs/foo/bar:refs/qux/baz'.
In English that means: resolve 'refs/foo/bar' on the remote server,
fetch the object it points to, and create a local reference
'refs/qux/baz' that points to that thing.

However, since Git 1.8.3 (released in 2013) it is also allowed to
write '$COMMIT_SHA:refs/qux/baz'. What that does is: fetch object
$COMMIT_SHA from the server, and create a local 'refs/qux/baz' that
points to that thing.

This commit changes the refspec used for "persistent ref" CI fetches.
We already know what commit SHA persistent refs point to so there is
no need to have Git resolve the persistent ref again during a CI
build.

- add changelog

Enable multipart transfers for S3 copying

See merge request gitlab-org/gitlab!51267

This is a follow-up to
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/50922. Multithreaded,
multipart transfers are only enabled if the file is above 5 GB or the
multipart chunk size is explicitly set.

We now set the chunk size to 10 megabytes (the AWS SDK default) to make
file copies faster.

This commit also updates fog-aws to v3.8.0 to work properly with server
side encryption parameters.

CHANGELOG: https://github.com/fog/fog-aws/blob/master/CHANGELOG.md

Implement declarative enums abstraction

See merge request gitlab-org/gitlab!50698

Update GraphqlExtractor return value to be original hash

See merge request gitlab-org/gitlab!51596

Merge branch '297364-flaky-test-spec-services-merge_requests-export_csv_service_spec-rb-29-mergerequests' into 'master'

test: Fix flaky expectations

See merge request gitlab-org/gitlab!51457

Merge branch '296976-the-open-list-in-boards-with-swimlanes-applied-is-mislabeled-as-backlog' into 'master'

Rename Backlog list to Open for Swimlanes

See merge request gitlab-org/gitlab!51539

Remove merge_ref_auto_sync flag

See merge request gitlab-org/gitlab!51624

Instead of spreading the enum information all around the codebase
between different modules like models and GraphQL types, we can set a
single source of the truth for the Enum values.

To do so, we should promote the enums to be first class members of the
project by giving them a new top level directory to live in.

Remove test_failure_history flag

See merge request gitlab-org/gitlab!51464

Remove github_import_pull_request_reviews feature flag

See merge request gitlab-org/gitlab!51334

Override tertiary button mix blend mode for darkmode

See merge request gitlab-org/gitlab!51349