Synchronously removes the index on project_statistics for wiki
size and project id, only for GitLab.com

Changelog: removed

Synchronously removes the index on project_statistics for packages
size and project id, only for GitLab.com

Changelog: removed

- merge_requests.head_pipeline_id_convert_to_bigint
- merge_request_metrics.pipeline_id_convert_to_bigint
- merge_trains.pipeline_id_convert_to_bigint
- vulnerability_feedback.pipeline_id_convert_to_bigint
- vulnerability_occurrence_pipelines.pipeline_id_convert_to_bigint

Changelog: changed

GitLab 17.2 shipped a migration
(https://gitlab.com/gitlab-org/gitlab/-/merge_requests/158711) that
dropped `p_ci_builds.id`. However, we received a number of reports of
users who had unrelated sequences owned by `p_ci_builds.id`, so the
migration failed because the objects depended on that column existing.

To allow migrations to go through, scan the system catalog for all
sequences owned by either `p_ci_builds` or `ci_builds`. Generate the
`ALTER SEQUENCE` statement to update the ownership of the sequence
using the technique described in
https://wiki.postgresql.org/wiki/Fixing_Sequences.

Note that we could run all 600+ `ALTER SEQUENCE` commands to bring the
database to a consistent state, but to minimize risk we target only on
the ones to allow the CI builds migration to proceed.

Changelog: fixed

Relates to https://gitlab.com/gitlab-org/gitlab/-/issues/468541

## What does this MR do and why?

Add and backfill project_id for evidences.

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/evidences.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.

## How to verify

We have assigned a random backend engineer from ~"group::compliance" 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/evidences.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

- include concerns that can be reused
- implement methods and classes for Discussion
- add specs
- add adding type to notes migration

Changelog: other

- needed to remove lazy creation of user_details
- background migration to go over users table and
  find users w/o the needed entries and create them.

Changelog: other

Introduces the Ci::Tagging model to replace
the ActsAsTaggableOn::Tagging model.

Remove incorrect model class.

Introduces the Ci::tag model which implements
the API needed by ActsAsTaggableOn::Tag to tag
jobs.

New column to store HMAC secret and
initialization vector. These secrets
will be used for authentication of
external status checks

Changelog: added
EE: true

Replaces the non-partitioned FK with a partitioned one
Changelog: other

Add a migration to add maximum_storage_bytes bigint columns
to zoekt_indices table.

Changelog: other
MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/159382

Changelog: other

pm_affected_packages.

Changelog: added

Replaces the non-partitioned FK with a partitioned one
Changelog: other

Replaces the non-partitioned FK with a partitioned one
Changelog: other

Changelog: other

Add and backfill group_id for approval_group_rules_protected_branches.

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/approval_group_rules_protected_branches.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::source code" 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/approval_group_rules_protected_branches.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

Co-authored-by: Lorena Ciutacu <lciutacu@gitlab.com>

In a migration, set namespace_settings seat_control to 1 if
new_user_signups_cap is not null

Changelog: added

Add missing comma after
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/158372.

[skip-db-structure-check]

Changelog: added

This change adds a migration to remove NOT NULL constraint
on scan_result_policy_id for scan_result_policy_violations
as it will be replaced by approval_policy_rule_id.

Changelog: other

Replaces the non-partitioned FK with a partitioned one
Changelog: other

Changelog: other

Changelog: added
EE: true

Changelog: other

- Add MemberRoleRelation to GroupGroupLink model
- Update non_guests scope in GroupGroupLink model
- Update UserMemberRolesInGroupsPreloader to include group links

Changelog: added

Update the resolver to filter and sort results

Changelog: added

Reduce this value to match the maximum depth used for legacy epics

Changelog: changed
EE: true