Transition dast_pre_scan_* tables to gitlab_sec

Arpit Gogiarequested to merge
472362-472363-transition-pre-scan-tables into master

What does this MR do and why?

Transitions the table dast_pre_scan_verifications and dast_pre_scan_verification_steps to gitlab_sec schema

This is part of a larger initiative to decompose the tables used by Secure: &14196 (closed)

Changing two tables in one MR

Changing these tables both in one MR since the tables are part of a feature that has been deprioritised and is behind a feature flag: gitlab-org/quality/triage-reports#17479 (comment 1898514196). The feature has completed frontend work but partially completed backend work and removing the feature would require frontend effort that the DAST team currently doesn't have capacity for.

The tables do not have any rows on production:

dast_pre_scan_verifications https://console.postgres.ai/gitlab/gitlab-production-main/sessions/31323/commands/97225

dast_pre_scan_verification_steps https://console.postgres.ai/gitlab/gitlab-production-main/sessions/31323/commands/97226

FAQ: &13043 (closed)

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #472362 (closed) #472363 (closed)

Edited by Arpit Gogia

Merge request reports