In https://gitlab.com/gitlab-org/gitlab/-/issues/334132 it was
identified that the `max_seats_used` of `GitlabSubscription` was not
correctly resetting when a new term starts (e.g. subscription renewal)

The wrong resetting logic was fixed by
https://gitlab.com/gitlab-org/gitlab/-/issues/334132.

This MR fix the existing wrong `max_seats_used` values in a background
migration script.

Changelog: fixed

Swaps FK for ci_variables.project_id to projects

Changelog: changed

Swaps FK for ci_triggers.project_id to projects

Changelog: changed

Fixes a race condition when draft notes exist on a line in a whitespace
diff but would end up getting an incorrect `line_code` set.
This is fixed by saving the `line_code` property into the database
to better match what the notes table does.

Changelog: fixed

Closes https://gitlab.com/gitlab-org/gitlab/-/issues/340815

Swaps FK for vulnerability_statistics.latest_pipeline_id to ci_pipelines

Changelog: changed

This commit fixes cross database queries for the runner.
We are leveraging disable_joins setting to make 2 SQL queries
instead of 1 in order to prevent cross database query.

Changelog: performance

- Drop column
- Add specs

Changelog: removed
MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/78665

This index has been replaced by
index_cluster_agent_tokens_on_agent_id_status_last_used_at

Changelog: other

Streamed audit events now include a new
HTTP header to allow event consumers to validate
the event origin.

Changelog: added

Swaps FK for vulnerability_occurrence_pipelines.pipeline_id to ci_pipelines

Changelog: changed

Swaps FK for dast_profiles_pipelines.ci_pipeline_id to ci_pipelines

Changelog: changed

This field stores the runner's token expiration time.

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

Swaps FK for merge_trains.pipeline_id to ci_pipelines

Changelog: changed

Removes FK for ci_triggers to users

Changelog: changed

Swaps FK for merge_requests.head_pipeline_id to ci_pipelines

Changelog: changed

Removes FK for ci_sources_pipelines to projects

Changelog: changed

Adds application_settings and container_repositories
columns needed to support the import of
container_repositories into the registry metadatabase.

Changelog: other

We already have ci_running_builds FK to ci_builds, and also an LFK from
ci_running_builds to projects.

Changelog: other

Removes FK for ci_pipeline_artifacts to projects

Changelog: changed

This adds an experiment for requiring credit card validation
before creating a new group when signing up.

Changelog: added

Add the new field so that runners can use it to determine their
token expiration time.

Changelog: added
Issue: https://gitlab.com/gitlab-org/gitlab/-/issue/30942

Initially only available to the Datadog integration and disabled with
feature flag

The summary field in the Vulnerability Finding Evidenced
is not used and can be removed.

Changelog: changed

In https://gitlab.com/gitlab-org/gitlab/-/merge_requests/77908 we
already added a ["loose foreign key"](
https://docs.gitlab.com/ee/development/database/loose_foreign_keys.html)
to replace this foreign key. Now that this has been running fine in
production we should be OK to remove the foreign key altogether.

This was added in a post-deployment migration as we want to ensure that
they have the correct code running with the loose foreign key in place
before we remove the foreign key to ensure that there isn't any lost
deletes.

Changelog: other

- Add a cron job and a limited capacity worker to delete package files
  in a decoupled and async way, taking the Package Registry a step
  closer to a scalable package file deletion approach.
- The cron job runs twice a day. It checks if there are any package
  files pending destruction, in which case it enqueues the limited
  capacity worker.
- The limited capacity worker picks up and destroys package files that
  are pending destruction one by one until all have ben deleted.
- Since the new jobs are very similar in functionality to the Dependency
  Proxy cleanup jobs, do some refactoring for reuse.

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

This change also introduces the necessary database tables.

Changelog: added
EE: true

In https://gitlab.com/gitlab-org/gitlab/-/merge_requests/77908 we
already added a ["loose foreign key"](
https://docs.gitlab.com/ee/development/database/loose_foreign_keys.html)
to replace this foreign key. Now that this has been running fine in
production we should be OK to remove the foreign key altogether.

This was added in a post-deployment migration as we want to ensure that
they have the correct code running with the loose foreign key in place
before we remove the foreign key to ensure that there isn't any lost
deletes.

Changelog: other

In https://gitlab.com/gitlab-org/gitlab/-/merge_requests/77908 we
already added a ["loose foreign key"](
https://docs.gitlab.com/ee/development/database/loose_foreign_keys.html)
to replace this foreign key. Now that this has been running fine in
production we should be OK to remove the foreign key altogether.

This was added in a post-deployment migration as we want to ensure that
they have the correct code running with the loose foreign key in place
before we remove the foreign key to ensure that there isn't any lost
deletes.

Changelog: other

In https://gitlab.com/gitlab-org/gitlab/-/merge_requests/77908 we
already added a ["loose foreign key"](
https://docs.gitlab.com/ee/development/database/loose_foreign_keys.html)
to replace this foreign key. Now that this has been running fine in
production we should be OK to remove the foreign key altogether.

This was added in a post-deployment migration as we want to ensure that
they have the correct code running with the loose foreign key in place
before we remove the foreign key to ensure that there isn't any lost
deletes.

Changelog: other

Add index_on_projects_path index back

Changelog: fixed

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

Remove FK for ci_daily_build_group_report_results to projects

Changelog: changed

To temporarily improve the performance of an upcoming data migration we
need to add an index on the Member state column. This index can be
removed after 14.8

Changelog: added

Changelog: added

in support of upcoming work on members table

Changelog: changed

The existing API deletes a single job's artifacts.

We already have a ci_pending_builds FK to ci_builds.
ci_builds in turn have a FK to projects. So this FK should
be safe to remove.

With this change when project is deleted, dependent ci_pending_builds
will either be:

- deleted via loose foreign keys
- deleted via FK cascade projects -> ci_builds -> ci_pending_builds

Changelog: other

Changelog: changed

Changelog: changed

Removes FK for ci_build_report_results to projects

Changelog: changed

Removes FK for ci_resource_groups to projects

Changelog: changed