Use the backfilled table as an index for a data migration on project_ci_cd_settings

Related to: #514242 (closed)

Why are we doing this work

Use the backfilled table as an index for a data migration on project_ci_cd_settings

Follow-up to Block use of pipeline variables for projects not using them:

Introduce a batched background migration that sets pipeline_variables_minimum_override_role to zno_one_allowedz in project_ci_cd_settings for projects that either don’t use pipeline variables - aren’t listed in the projects_with_pipeline_variables table.

The batched migration should reflect a basic SQL update query.

UPDATE project_ci_cd_settings
SET pipeline_variables_minimum_override_role = 1
WHERE project_id NOT IN (
  SELECT project_id FROM projects_with_pipeline_variables
);

Introduced solution

A sidekiq worker to run a migration to set pipeline_variables_minimum_override_role to no_one_allowed.

Since we decided not to migrate all projects at once, we're introducing a helpful tool to migrate projects within specific groups on demand.

Relevant links

Non-functional requirements

• Documentation:
• Feature flag:
• Performance:
• Testing:

Implementation plan

Verification steps