fix: Allow to set empty securityContext for all deployments

[ppawlowski]

Description

This pull requests adjusts the way how securityContext is created in each deployment managed by helm chart.
This change allows to provide no values for each securityContext . Since we provide pre-defined values for each of the deployment, now there will be a posibility to completly remove a securityContenxt values by assigining null value to the forge.podSecurityContext.

Related Issue(s)

#526

Checklist

• I have read the contribution guidelines
• Suitable unit/system level tests have been added and they pass
• Documentation has been updated
  • Upgrade instructions
  • Configuration details
  • Concepts
• Changes flowforge.yml?
  • Issue/PR raised on FlowFuse/helm to update ConfigMap Template
  • Issue/PR raised on FlowFuse/CloudProject to update values for Staging/Production

Labels

• Includes a DB migration? -> add the area:migration label

[hardillb]

Making things easier for OpenShift?

[ppawlowski]

Making things easier for OpenShift?

Correct.

Without this change spec.template.spec.securityContext values can be overrided only with custom vlaues. This change will allow to set empty spec.template.spec.securityContext .