Support different types of DAST scan
Problem to solve
Users may want to use different types of DAST scans in their apps.
A full scan may require too much time to complete, and so users will eventually disable the job. That's bad.
We should provide different predefined "scan profiles", and users will be able to set a different default.
Create different DAST profiles, that can be driven with variables:
- full (current one)
- active scan (see #7182)
Users can set variables at project/group level to define the scan type:
What does success look like, and how can we measure that?
Number of projects with a different default for DAST scan profile.