Post disabling cleanup of Limit CI_JOB_TOKEN_SCOPE feature

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

• Work on this issue
• Close this issue

We have disabled the Limit CI_JOB_TOKEN_SCOPE feature in 18.0, Now, we need to do cleanup of related code in frontend and backend. Also we need to do Data migrations related to it. This issue tracks all these tasks

Tasks

• Frontend MR to cleanup all the code related to this feature. WIP MR
• We create a backend MR with a migration to delete all the records in the ci_job_token_project_scope_links table where directon value is :outbound. First we need to investigate if this needs to be a Post deployment migration or a batched background migration depending upon the time taken to run the migration.
• [Optional] If in the previous step, we decide to go for a batched background migration, we need to wait for the next required stop release and then finalize the batched background migration
• Backend MR to cleanup all the code related to this feature. Remove all deprecated GQL fields. We should remove all references to direction column in the ProjectScopeLink model and also add a column ignore rule to ignore the direction column in the ProjectScopeLink model. Get this MR merged and deployed - Docs on dropping a DB column without downtime
• Create a backend MR with the DB migration to drop the direction column from the ci_job_token_project_scope_links table
• Create an MR to remove the column ignore rule that was added earlier that ignored direction column in the ProjectScopeLink model.