Enable Framework Selection During Helm Installation

[AdonisOkpidi]

Overview

Currently, all frameworks are scanned by default, and there is no existing mechanism to control this behaviour via Helm.

Problem

During installation, it is not possible to specify the framework required for a specific cloud provider. As a result, I must manually extract the necessary controls from the JSON reports, which can be a time-consuming process.

Solution

1. Introduce a capability similar to Trivy Operator, allowing users to specify one or multiple frameworks in the values.yaml file. See Trivy Operator example.

   specs: 
   - k8s-cis-1.23 
   - k8s-nsa-1.0
   - k8s-pss-baseline-0.1
   - k8s-pss-restricted-0.1

Additionally, enable this configuration through the --set flag in the Helm install command.

Additional Information

# I would want to be able to set for GKE:
frameworks:
- AllControls
- cis-v1.23-t1.0.1

# For AKS:
frameworks:
- cis-aks-t1.2.0

[dwertent]

We need to define the behavior when a user triggers a scan manually via the API and specifies frameworks that differ from the "default" frameworks. My intuition is that the API-triggered frameworks should override the "on-installation" frameworks list. Therefore, the naming should be: defaultFrameworks, which by default includes allControls, mitre, and nsa (as it currently does).

[dwertent]

1. Add the config
2. Update the dependencies
3. Add the code to the Operator and release the Operator
4. Add the default values to the Helm and release the Helm

[slashben]

@entlein will take this issue

[entlein]

Thanks for helping me with my first contribution