consider putting details about errors in `models.VulnerabilityResults`

[josieang]

This was discussed in: https://github.com/google/osv-scanner/pull/501#discussion_r1401646226

Return error codes don't seem to be the right way to report what combination of vulnerability, called vulnerabilities, license violations. It's simpler to just return 0 or 1, and put the details about what kinds of issues are present in the json or models.VulnerabilityResults output.

[github-actions[bot]]

This issue has not had any activity for 60 days and will be automatically closed in two weeks

[github-actions[bot]]

Automatically closing stale issue

[oliverchang]

@cuixq would this be interesting for v2?

[cuixq]

yes, we would like to re-design error types in v2 https://github.com/google/osv-scanner/issues/636, and this is related.