Provide job and artifact path as context in SBOM ingestion errors

Proposal

If errors are encountered while ingesting SBOMs the UI will show a generic name for the gzipped reports like report-1(1) and provide no further context. This makes it hard to understand where the error was encountered since the CycloneDX report could have been picked up from a number of a jobs, and within a job, from a number of paths.

Usable errors are part of a good user experience because when things inevitable error out, they help users remediate the problems on their own, and if they require further assistance, they provide valuable information for support.