fix(k8s): check all results for vulnerabilities

[afdesk]

Description

Previously, vulnerabilities were checked only for the first result of a resource. Now, all results are scanned.

Before

Workload Assessment
┌───────────┬──────────────────┬───────────────────┬───────────────────┬───────────────────┐
│ Namespace │     Resource     │  Vulnerabilities  │ Misconfigurations │      Secrets      │
│           │                  ├───┬───┬───┬───┬───┼───┬───┬───┬───┬───┼───┬───┬───┬───┬───┤
│           │                  │ C │ H │ M │ L │ U │ C │ H │ M │ L │ U │ C │ H │ M │ L │ U │
├───────────┼──────────────────┼───┼───┼───┼───┼───┼───┼───┼───┼───┼───┼───┼───┼───┼───┼───┤
│ test      │ Pod/postgres-pod │   │   │   │   │   │   │ 1 │ 4 │ 9 │   │   │   │   │   │   │
└───────────┴──────────────────┴───┴───┴───┴───┴───┴───┴───┴───┴───┴───┴───┴───┴───┴───┴───┘
Severities: C=CRITICAL H=HIGH M=MEDIUM L=LOW U=UNKNOWN

After

Workload Assessment
┌───────────┬──────────────────┬─────────────────────┬───────────────────┬───────────────────┐
│ Namespace │     Resource     │   Vulnerabilities   │ Misconfigurations │      Secrets      │
│           │                  ├───┬────┬────┬───┬───┼───┬───┬───┬───┬───┼───┬───┬───┬───┬───┤
│           │                  │ C │ H  │ M  │ L │ U │ C │ H │ M │ L │ U │ C │ H │ M │ L │ U │
├───────────┼──────────────────┼───┼────┼────┼───┼───┼───┼───┼───┼───┼───┼───┼───┼───┼───┼───┤
│ test      │ Pod/postgres-pod │ 3 │ 31 │ 20 │ 1 │   │   │ 1 │ 4 │ 9 │   │   │   │   │   │   │
└───────────┴──────────────────┴───┴────┴────┴───┴───┴───┴───┴───┴───┴───┴───┴───┴───┴───┴───┘
Severities: C=CRITICAL H=HIGH M=MEDIUM L=LOW U=UNKNOWN

Related issues

• Close bug(k8s): inconsistent results from summary and all report on k8s workload #7937

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).