feat(plugin-barman-cloud): add possibility to unset runAsUser and runAsGroup

[Pidu2]

This PR addresses the requirements of #673.

In an OpenShift environment, you usually do not want to set runAsUser or runAsGroup to something specific, instead it is chosen automatically by the cluster to a random value.

With this change, runAsUser and runAsGroup can be set to null and are therefore skipped when rendering.

---

values.yaml

containerSecurityContext:
  runAsUser: null
  runAsGroup: null

result

❯ helm template . --values values-barman.yaml -s templates/deployment.yaml | yq .spec.template.spec.containers.0.securityContext
allowPrivilegeEscalation: false
capabilities:
  drop:
    - ALL
readOnlyRootFilesystem: true
seccompProfile:
  type: RuntimeDefault

[phisco]

@Pidu2 can you fix the DCO failure in CI? otherwise LGTM 🙏

[bmfdi]

I'd really like to have this merged into main. Could you please continue to work on this topic or should we open a new MR?

[Farioko]

When is this getting merged?

[salmar-pnsf]

This is a non trivial change that blocks deployment on e.g Openshift. Can we get this merged?

[Pidu2]

@phisco who can get this merged? :)

[phisco]

Closing and reopening to get ci to run

[phisco]

Can you rebase, @Pidu2? I'll merge it once ci is green.

[Pidu2]

@phisco rebased, I think someone needs to approve the CI runs.

[Pidu2]

I don't think the broken CI is caused by my change 😅