Improve component detection error handling

[sfoslund]

We have been seeing support requests in which the component detection library throws errors in a scan, usually due to malformed packages present on the machine, and the SBOM tool surfaces those errors before continuing the scan. This can be confusing to users, who see these errors (which are displayed in red, along with a full stack trace) and think that the SBOM generation failed. Further, this can obscure other, more critical errors.

We should wrap component detection errors such that they are only displayed as warnings when they are not critical and the scan can continue.