Migrate ci_builds.options and ci_builds.yaml_variables to a different table

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Overview

We should prepare a background migration that will move ci_builds.options to ci_build_metadata.processing_options. If we get the archival policies right, this should be a reasonable amount of data that we should be capable of migrating. We should do this because the ci_builds.options column is processing-time-only data that does not need to live in ci_builds.

UPDATE: During CI storage optimization - Phase 3: remove legac... (&18271) we will be able to migrate ci_builds.options and ci_builds.yaml_variables to ci_job_definitions in a deduplicated way. This means we can then drop the 2 columns in ci_builds entirely.