Each pod should explicitly declare it's securityContext

[tolusha]

Is your task related to a problem? Please describe

For best security practices, the securityContext under each Pod must be fully declared in order to clearly communicate the workload's security posture. In order to be declarative about their security posture, Pods must define every parameter available in its securityContext and each container's securityContext.

Continuation of #18362

Describe the solution you'd like

Explicitly define container SecurityContext:

      securityContext:
        capabilities:
          drop:
            - ALL
        allowPrivilegeEscalation: false
        runAsNonRoot: true

Describe alternatives you've considered

No response

Additional context

No response

[l0rd]

@tolusha to clarify: this issue is server side (i.e. for Che operands) and not workspace side (we need a distinct issue for that)?

[tolusha]

It is for all pods running on the cluster, so che-operator + DWO are involved.