Do not propagate parsing exceptions to clients for `pipelineFindings`
What does this MR do and why?
It is expected to receive a malformed report artifact so there is no point to raise parsing errors back to the user for the GraphQL pipelineFindings
query.
This MR introduces a change to capture parsing errors and respond with an empty response body if a parsing error happens.
Related to !73988 (merged).
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.