This commit adds support for Gitaly's DiffService.DiffBlobs() RPC which
can be used to compute the diffs between two points in a repository.

Changelog: added

Changelog: fixed

This addresses misrouted jobs when changing a worker attribute. During
the deployment period where both new and old versions are running,
jobs scheduled by the new processes could be picked up by an older
process and routed with a wrong combination of store and queue.

See https://gitlab.com/gitlab-com/gl-infra/scalability/-/issues/3497#note_2007088595

- Update group links create & update service to accept
member_role_id param
- Fetch custom roles in the frontend
- Both changes are behind feature-flag,
assign_custom_roles_to_group_links

Changelog: added
EE: true

Remove FFs wiki_front_matter and wiki_front_matter_title.

Changelog: added

- Remove Packages::Composer::CacheFile model.
- Remove composer cache file sidekiq workers.
- Remove composer cache file creator.
- Remove composer cache file database records.

Changelog: removed

Add and backfill namespace_id for epic_issues.

This table has a
[desired sharding key](https://docs.gitlab.com/ee/development/database/multiple_databases.html#define-a-desired_sharding_key-to-automatically-backfill-a-sharding_key)
configured ([view configuration](https://gitlab.com/gitlab-org/gitlab/-/blob/master/db/docs/epic_issues.yml)).

This merge request is the first step towards transforming the desired sharding key into a
[sharding key](https://docs.gitlab.com/ee/development/database/multiple_databases.html#defining-a-sharding-key-for-all-cell-local-tables).

This involves three changes:

- Adding a new column that will serve as the sharding key (along with the relevant index and foreign key).
- Populating the sharding key when new records are created by adding a database function and trigger.
- Scheduling a [batched background migration](https://docs.gitlab.com/ee/development/database/batched_background_migrations.html)
  to set the sharding key for existing records.

Once the background migration has completed, a second merge request will be created to finalize the background
migration and validate the not null constraint.

We have assigned a random backend engineer from ~"group::product planning" to review these changes. Please review this merge
request from a ~backend perspective. The main thing we are looking to verify is that the added column and association
match the values specified by the [desired sharding key](https://gitlab.com/gitlab-org/gitlab/-/blob/master/db/docs/epic_issues.yml)
configuration and that backfilling the column from this other table makes sense in the context of this feature.

When you are finished, please:

1. Trigger the [database testing pipeline](https://docs.gitlab.com/ee/development/database/database_migration_pipeline.html)
   as instructed by Danger.
1. Request a review from the ~backend maintainer and ~database reviewer suggested by Danger.

If you have any questions or concerns, reach out to `@tigerwnz` or @manojmj.

This merge request was generated by a once off keep implemented in
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/143774

This change was generated by
[gitlab-housekeeper](https://gitlab.com/gitlab-org/gitlab/-/tree/master/gems/gitlab-housekeeper)
using the Keeps::BackfillDesiredShardingKeySmallTable keep.

To provide feedback on your experience with `gitlab-housekeeper` please comment in
<https://gitlab.com/gitlab-org/gitlab/-/issues/442003>.

Changelog: other

Contributes to https://gitlab.com/gitlab-org/gitlab/-/issues/467850

**Problem**

The new strict version of `go-get` validation
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/156860 returns 404
page when the requested project is not found.

That breaks the support for redirected routes.

For example, a project like `gitlab.com/namespace/project` can be
accessed via `go get`.

```
go get gitlab.com/namespace/project
```

Before the restriction we would return a 200 response code, go will
follow redirects and process the downloading the package.

The new strict version, will return 404 response code and stop `go get`
execution.

**Solution**

Add a verification for redirect routes. When user requests the old path,
`go get` response will be 200 and include a link to the new project
path.

Changelog: fixed

This is a follow-up to
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/154577

Like the earlier MR, this is also a refactoring to remove the `if
endpoint_scope...` checks in the code. For this MR, as the title says,
we're removing methods in the shared helper module into inline helper
methods in the individual endpoint (project, group, instance) classes.

Changelog: added

Previously the query for finding PostgreSQL sequences owned by a table
erroneously picked up unrelated sequences. For some reason, after a
`pg_upgrade` from PostgreSQL 13 to 14, some sequences appear to have
new entries in the `pg_depend` table that are associated with
`p_ci_builds` or `ci_builds` columns. As a result, the partitioning
code would change the ownership to the wrong column. For example:

```
         seq_name          | table_name  |   col_name   | deptype
---------------------------+-------------+--------------+---------
 ci_builds_id_seq          | p_ci_builds | id           | a
 push_rules_id_seq         | ci_builds   | id           | n
 push_rules_id_seq         | ci_builds   | partition_id | n
 security_trainings_id_seq | p_ci_builds | id           | n
 security_trainings_id_seq | p_ci_builds | partition_id | n
 term_agreements_id_seq    | p_ci_builds | commit_id    | a
(6 rows)
```

Previously `sequences_owned_by(p_ci_builds)` would return the
following items, even though the ownership for each of the items had
not changed:

- ci_builds_id_seq
- security_trainings_id_seq
- term_agreements_id_seq

To avoid assigning sequences to the wrong owner, we need additional
filtering for `pg_class` to ensure we only look at sequence owners.

Relates to:

* https://gitlab.com/gitlab-org/gitlab/-/issues/473337
* https://gitlab.com/gitlab-org/gitlab/-/issues/468541

Changelog: fixed

Changelog: fixed
MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/159215

updates copy for workflow rules and rules failure messages

The Metrics Dashboard (used for monitoring apps deploying using gitlab)
was deprecated in 14.7 and removed from the product in 16.0.
This commit cleans up a portion of the dead code.

https://gitlab.com/groups/gitlab-org/-/epics/10107

The Metrics Dashboard (used for monitoring apps deploying using gitlab)
was deprecated in 14.7 and removed from the product in 16.0.
This commit cleans up a portion of the dead code.

https://gitlab.com/groups/gitlab-org/-/epics/10107

The Metrics Dashboard (used for monitoring apps deploying using gitlab)
was deprecated in 14.7 and removed from the product in 16.0.
This commit cleans up a portion of the dead code.

https://gitlab.com/groups/gitlab-org/-/epics/10107

We are dropping the work_item_types.namespace_id
column, so we first need to ignore it in this release (17.3)
so it can be dropped from the DB in 17.4

Changelog: performance

Only in rspec context

Old data has DF score as high even with
1 deployment per month. This data migration
recalculates all previous DF scores to
correct ones.

Changelog: added
EE: true

Prevents errors if we rename models/columns of referenced data

Changelog: changed

Less retries, shorter sleep intervals. Partitions are synced often
enough, if lock can not be obtained  move to the next one instead of
retrying as if it's a migration.

Merge branch 'security/limit-access-to-exports' into 'master'

See merge request gitlab-org/security/gitlab!4080

Changelog: security