Show information about security report schema validation problems in Vulnerability Report

Why are we doing this work?

Currently, we expose schema validation warnings only in the pipeline security tab. I think it would be more visible if we exposed those warnings or some kind of message in the Vulnerability Report section, see picture.

Implementation plan

1. Pass the hasParsingErrors and hasParsingWarnings flags to the frontend.
2. Render the warning message based on the flags' state.
   • If both are true: Parsing errors and warnings in pipeline.
   • If only hasParsingErrors is true: Parsing errors in pipeline.
   • If only hasParsingWarnings is true: Parsing warnings in pipeline.

Testing

• Make sure existing Secure E2E tests are not broken

Verification

As of writing this, the following project seems to have parsing errors: https://gitlab.com/gitlab-org/opstrace/opstrace/-/security/vulnerability_report.