Move security reports logic to backend
Problem to solve
Security Reports shown in Merge Request, Pipeline view and Project Security Dashboard are currently parsed and compared on frontend, using raw json artifacts. We should move that logic to the backend and provide a clean report API to the frontend, like junit reports do.
NB: Backend parsing is already being done as part of storing vulnerabilities in the database which should be completed in %11.8. When every reports will be parsed on backend, we can start working on this.
This step is a technical requirement before being able to do some changes like extending the json reports.
Proposal
Create a new API to deliver reports content to frontend, using a ready to use and common json entity. Such entities already exist as part of the Group Security Dashboard and should be reused to provide the same structure everywhere and allow frontend to reuse standard components.
Though, as it has not yet been decided if every branches will leverage the DB storage, we may need to adapt this to non persisted records.
What does success look like, and how can we measure that?
(If no way to measure success, link to an issue that will implement a way to measure this)