feat(misconf): Improve scan results messaging

[simar7]

When reporting misconfiguration scanning results we can be more descriptive about how many "total" files were scanned and how many "misconfigured" files were found.

See context below for details:

Trivy successfully scans the ARM template. I think the message Detected config files: 0 might be misleading.

@simar7 The issue is that the Azure state for the scan was empty and no checks were applied to it, so Trivy reported that 0 configs were detected.

Originally posted by @nikpivkin in #6123 (comment)

[nikpivkin]

@simar7 Should we only change the wording of the Detected config files: ... message, or should we add some other messages? Does it make sense for users to report how many files have been checked?

[simar7]

@nikpivkin as you brought up here this result contains passed items as well. I looked into adding more logic to decouple that but didn't finish the implementation.

Ideally if we can show the user how many "relevant" files were scanned by the IaC scanner, it would be more relevant. In this case a "relevant" file would be the one that we've processed through the scanner. Currently we don't keep track of this AFAIK.

[simar7]

I've created #7473 as I think it is sufficient to show the count of files scanned and the count of "relevant" config files found that were scanned. Besides this, I'm not sure what much we can do in this case to improve it.

[nikpivkin]

@simar7 Is there a need to report how many total files were scanned? We can report the number of files with misconfigurations.

[simar7]

I think we're good for now.