fix: handle BLOW_UNKNOWN error to download DBs

[DmitriyLewen]

Description

We found that GCR periodically returns BLOW_UNKNOWN error - #8020
We assume that this is related to their cache.

But in any case, we need to handle this error and check other repositories if loading a repository returns BLOW_UNKNOWN error.

Issues

• Close Fall back repositories with BLOB_UNKNOWN errors #8069

Checklist

• I've read the guidelines for contributing to this repository.
• I've followed the conventions in the PR title.
• I've added tests that prove my fix is effective or that my feature works.
• I've updated the documentation with the relevant information (if needed).
• I've added usage information (if the PR introduces new options)
• I've included a "before" and "after" example to the description (if the PR is a user interface change).

[knqyf263]

Looks great!

[knqyf263]

@DmitriyLewen Do you think we should cut v0.58.1?

[DmitriyLewen]

Are there any other critical fixes?
It seems this bug is not very common and we may include this fix in v0.59.0.

But overall for the user experience we may cut v0.58.1

[knqyf263]

I don't see any other hotfixes. If we receive more reports of this error, we can cut v0.58.1.

[DmitriyLewen]

Yes, let's get more feedback from users.

[marcoschmidl]

Hey, I would really appreciate the 0.58.1 with the bug fix for the BLOB_UNKNOWN error. In my current project, I use Trivy for AKS and run it in a GitLab pipeline. In the past two weeks, I had the error a few times. The new release with the fix would be a quick solution without further workarounds.

[knqyf263]

You can track the milestone here.
https://github.com/aquasecurity/trivy/milestone/45

[DmitriyLewen]

Hello @marcoschmidl
Trivy has canary builds.
If you really need this fix - you can use this - https://github.com/aquasecurity/trivy/actions/runs/12195096688

[DmitriyLewen]

@aqua-bot backport release/v0.58

[aqua-bot]

Backport PR created: #8121

[marcoschmidl]

Thanks for your support @DmitriyLewen @knqyf263