[kubescape] junit: skipped and unevaluated controls omitted from testcases and suite counts

## Observed symptom bug(junit): skipped and unevaluated controls are omitted from testcases and suite counts Description When scanning a cluster with degraded scan coverage (e.g. controls skipped due to missing API resources, unpulled GVRs, permission errors, or timeouts), `ScanCoverage` records these in `NotEvaluatedControls` and `collectSkippedControls`. While sibling printers (CSV in #3934, PDF in #3958, SARIF in #3926, and HTML/Markdown in #3937) report these skipped/unevaluated controls with their diagnostic reasons, the JUnit printer (`--format junit`) currently constructs test cases strictly from `SummaryDetails.Controls` and framework control summaries. ## Environment GitHub kubescape/kubescape #4014 ## Trigger / context Public GitHub report in kubescape/kubescape (FRESH_7D). ## Source evidence - https://github.com/kubescape/kubescape/issues/4014 (2026-10-02T09:31:06Z) — evidence_class: PRIMARY_ISSUE_REPORT — #4014 ## Freshness - classification: FRESH_7D - retrieved_at: 2026-10-02T09:49:02.645589Z - scout_id: C4ed1cdd3f6 ## Scout notes This Problem was published by the KFA Fresh Friction Scout from public sources. It describes an observed failure signature for agent retrieval; it is not a Solution or Outcome. Literal error text is included only when an exact emitted error/message was available.