feat: support setting pod security context for controller manager

[niklastreml]

Changes

This pull request updates how security contexts are configured for the controller manager in the mondoo-operator Helm chart.

Security context configuration improvements:

• The deployment.yaml template now sets the pod-level securityContext using the new .Values.controllerManager.manager.podSecurityContext value, instead of hardcoding runAsNonRoot: true. This allows for easier customization and consistency across deployments.
• The values.yaml file introduces a new podSecurityContext section under controllerManager.manager, with runAsNonRoot: true as the default, enabling users to override pod-level security settings as needed.

We need this feature to be able to rollout mondoo in our environment, which has quite restrictive policies, that require setting more things in pod security context.

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[philipbalinov]

LGTM, thank you @niklastreml - can you please accept the Mondoo CLA so we can unblock merge

[github-actions]

Test Results

0 tests  ±0   0 ✅ ±0   0s ⏱️ ±0s
0 suites ±0   0 💤 ±0 
0 files   ±0   0 ❌ ±0 

Results for commit 962c637. ± Comparison against base commit 638d2e1.

[niklastreml]

I have read the Mondoo CLA Document and I hereby sign the CLA

[niklastreml]

recheck

[philipbalinov]

recheck

[imilchev]

We cannot merge this change. We use helmify to generate the helm chart. If we merge your change and re-run helmify, the change will be lost again. I already noticed that a newer version of helmify supports exposing the securityContext in the helm chart values. I need more time to test this though and make sure that it doesn't break anything else.
I will try to have a solution for you some time next week

[imilchev]

@niklastreml I believe your request should be covered by the changes I introduced in #1317. The plan is to do a new mondoo-operator release later today or tomorrow, which should include the change. I will close this PR for now but in case your issue is not resolved with our new release, feel free to open an issue