Catch all Security Report related errors

What does this MR do and why?

For DS in Limited availability we want to ensure that we will not break user's pipelines due to Vulnerability Report API. For that reason we will catch all errors and ignore them.

Following this MR and going forward we will work on adding metrics of how often this is failing. This can be done in 2 ways:

• Either update the API to send through headers additional information like the scan UUID and if this is the last attempt to call this API. In case it is we send a metric of the DS job failure in the backend.
• We instrument the DS analyzer to send empty security reports and we update the backend to manage an empty list of vulnerabilities.

Related issues

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before	After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.