Refactor NeuVector Helm values.yaml & questions.yaml to be more easily consumable and less error prone

[frank-at-suse]

Issue:

• feat: expose the imagePullPolicy parameter for every container as a Helm value neuvector/neuvector-helm#246 (comment)
• Support env vars for enforcer neuvector/neuvector-helm#224 (comment)
• [Feature Request] spec.template.metadata.annotations on controller deployment neuvector/neuvector-helm#178 (comment)
• Document controller.configmap.data neuvector/neuvector-helm#160 (comment)
• proxy configuration inside helm configuration? neuvector/neuvector-helm#99 (comment)

As well as numerous other community complaints (i.e. container runtime selection)

Problem

NeVector Helm chart is difficult to consume and causes issues with installation

Solution

This PR addresses several issues with consuming the NeuVector Helm chart - namely embedding YAML documents within YAML documents (not best practice)., exposing otherwise useful buried configuration options as top-level values, slipstreaming in to this chart the 'monitoring' chart, and presenting questions.yaml with a much more user-friendly format.

Engineering Testing

Manual Testing

Only issue encountered is that the prometheus-exporter image is not in the Rancher Prime repository, is the system default registry is pointing to Rancher Prime repo, or any repo built via a Rancher release's images.txt, the monitoring deployment will fail.

Backporting considerations

None

[frank-at-suse]

Closing this one to do upstream chart first