Resolve "Transition dast_profile_schedules to loose foreign keys"
What does this MR do and why?
As part of the security database decomposition effort, this MR transitions the dast_profiles_schedules
tables to the new db.
This is the relevant issue
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.
How to set up and validate locally
Related to #472361 (closed)
Edited by Schmil Monderer