Changelog: fixed

This reverts merge request !183259

In addition, we unify all the usage in a single place.

Changelog: fixed

Using the same create service for both REST API and GraphQL improves
the consistency and DRY.

This foreign key caused the incident
https://gitlab.com/gitlab-com/gl-infra/production/-/issues/19474 . It
was added in
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/177799 . The
problem is that we added a foreign key before adding an index. This
means that all statements like `DELETE FROM projects ...` will need to
scan the entire `merge_request_diff_files` table to check if the foreign
key is valid. This was causing timeouts.

In order to resolve the incident we've already manually deleted this
migration on GitLab.com . This MR additionally adds another migration to
remove the foreign key to clean up any environments where this migration
may have already run.

Given that configurable statuses functionality
should only be available for Premium and Ultimate
users, we need to ensure the status widget is
EE-only.

This commit moves the status widget-related classes
under the EE namespace to achieve that.

Changelog: added

This adds `diff_files_metadata` endpoint for each resource that
we support in rapid diffs (e.g. `MergeRequest`, `Commit` and
`Compare`).

This is behind `rapid_diffs` FF.

This MR adds an API endpoint to allow a user to perform bulk placeholder
reassignments by CSV upload without interacting with the GitLab UI.

Download endpoint MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/183360
Related issue: https://gitlab.com/gitlab-org/gitlab/-/issues/513794

This is meant to more clearly denote groups of tables that are
cell-local. These cell-local tables should not have references to
organization tables.

This adds internal event tracking to several events
in placeholder reassignment.

Changelog: other

Changelog: other

Changelog: changed

- sometimes getModel returns nul and the ui errors
- add a check for this
- update tests

Changelog: fixed

Previously, the file size check required a complete graph walk,
which was slow.
This change optimizes the process by using an existing method
that checks only the quarantine directory, improving performance.

Additionally, since this is an EE feature,
a new EE-specific FileSizeCheck class was introduced
to retrieve and apply the push rule file size limit

Changelog: changed
EE: true

Remove only create validation of
validate_only_one_sharding_key_present
and validate_imported_entity_type

Changelog: other

Add a callback to backfill project with pipeline variables table on new records
Address all the comments
Skip id primary key in favor of project_id
Add a trigger function instead of model callback
Add a trigger migration
Allow projects_with_pipeline_variables cross database

Changelog: added

So we can delete top level groups without reloading the page

In GitLab 17.6, the package protection feature was made generally
available. But, this realease did not include
the deletion package protection,
see https://gitlab.com/gitlab-org/gitlab/-/issues/472655 .

The attribute `minimum_access_level_for_delete` that was introduced
in the MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/179739 .

This attribute is integrated in this MR in order to prevent the deletion
of delete protected packages.

At the moment, the attribute `minimum_access_level_for_delete` cannot be
updated via UI, REST nor GraphQL API. This possibility will be added in
a future iteration.

Changelog: added

Changelog: other

- Behind feature flag `vscode_extension_marketplace_settings`
- https://gitlab.com/gitlab-org/gitlab/-/issues/508977

Changelog: changed

Unify the provide data names.

This table stores the CI pipeline inputs values configured when creating
a pipeline schedule. It belongs to a pipeline schedule, ensures that the
input keys are unique, and encrypts the input values. It is on the
gitlab_ci database schema because pipeline schedules are also stored on
the CI schema.

Changelog: added
Issue: https://gitlab.com/gitlab-org/gitlab/-/issues/519960

Bump PG default version in preparation for PG17

Changelog: changed

## What does this MR do and why?

Add and backfill project_id for deployment_merge_requests.

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/deployment_merge_requests.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 the following changes:

- Adding a new column that will serve as the sharding key (along with the relevant asynchronous index).
- 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 add a foreign key and not null constraint.

## How to verify

We have assigned a random backend engineer from ~"group::environments" 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/deployment_merge_requests.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 @shubhamkrai.

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::BackfillDesiredShardingKeyLargeTable keep.

To provide feedback on your experience with `gitlab-housekeeper` please create an issue with the
label ~"GitLab Housekeeper" and consider pinging the author of this keep.

Changelog: other

When the merge request source branch was ambiguous in the source
project, detached merge request pipelines would pick commit SHA
associated with the tag instead of the merge request's branch.

We fix that by using `source_branch_ref` instead of `source_branch` in
the places deciding the commit used by detached merge request pipelines.

Changelog: fixed

Changelog: other

Accepting `inputs` parameter as Hash.

Ensures the frontend link so the docs