Store DAST scan results into the database

Problem to solve

Data from DAST reports should be in the database, and consumers should use that backend instead of the raw JSON report.

This is required in order to present DAST results in a group-level Security Dashboard.

Further details

If consumers need to elaborate or aggregate data from many reports (e.g., group level features) it is not possible to use artifacts for that without heavily affecting performances.

Proposal

Save DAST reports in the database when they are collected from the Runner. Make this information available to the frontend via backend calls.