starboard-exporter release v1.0.0

starboard-exporter now supports kubescape! In addition to Trivy VulnerabilityReports, starboard-exporter now also supports reconciliation of Kubescape VulnerabilityManifests. Metrics have been updated to include a scanner label, indicating the source type of the data. Trivy and Kubescape can be used simultaneously, or individually toggled on and off. See the README for more information.
There is a breaking change to one of the CLI flags in this version. The --vulnerability-scans-enabled flag has been renamed to --trivy-vulnerability-scans-enabled in order to facilitate the new Kubescape scanner support. Users installing via the Helm chart are not affected.

Support for Kubescape vulnerability scanning via VulnerabilityManifest CR.
Scanner label (scanner="trivy" or scanner="kubescape") to all vulnerability metrics to distinguish between scanning sources.
Command-line flag --kubescape-vulnerability-scans-enabled.
Helm values configuration for enabling/disabling individual scanners under exporter.vulnerabilityReports.scanners.
Added backwards compatibility for legacy vulnerabilityReports.enabled Helm value (now enables Trivy scanner)

Renamed Trivy-specific functions and constants to include “Trivy” prefix to distinguish them from Kubescape components while maintaining shared metrics.
Command-line flag --vulnerability-scans-enabled to --trivy-vulnerability-scans-enabled (Breaking Change).