feat(misconf): Fallback to embedded check if needed

[simar7]

Today if the checks bundle is corrupt, we fallback to the checks that are embedded within Trivy.

This also comes in handy if we ever release a bundle with a check that is either syntactically incorrect or simply fails to load within the OPA engine for any reason. In this case today we skip this check and continue with the rest.

We can extend this idea further by falling back to the embedded implementation of this check, rather than skipping it altogether. This would allow us to fallback to a version which we guarantee runs with the version of Trivy being used.

It would also help us in cases where we release a new version of a check based on a new schema.