Store SAST scan results into the database
Problem to solve
Data from SAST reports should be in the database, and consumers should use that backend instead of the raw JSON report.
Also, it could be use to improve the performance of the existing Security Dashboard. See #6165 (closed)
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.
Save SAST reports in the database when they are collected from the Runner. Make this information available to the frontend via backend calls.
For the first iteration, it will not replace the artifact access. We can decouple this change and update the frontend independently.