fix: When submitting a scan job correctly check presence of reused reports before fetching credentials for each image

[festeveira]

Description

This PR fixes an issue in the logic that determines when to fetch private registry credentials. Previously, the code only checked whether the number of reused reports was greater than 0. This caused issues when the workload was composed of several images and at least one of the images had a corresponding ClusterSbomReport which was reused for the current scan; if one of the remaining images did not have a corresponding ClusterSbomReport and was from a private registry, it's credentials were not being fetched and added to the PodSpec's environment.

The updated logic instead compares the number of reused reports with the total number of container images. If the counts differ, it indicates that not all images have reusable reports, so the system will fetch the necessary private registry credentials for each image.

I have tested this change in my environment and it seemed to fix the related issue.

Related issues

• Close No private registry credentials for containers being analyzed by jobs where at least one image has a ClusterSbomReport #2809

Checklist

• I've read the guidelines for contributing to this repository.
• 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).