Don't add security context on <4.11 as OpenShift restricted SCCs do not tolerate it

[bennerv]

What this PR does / why we need it:

In <4.11, the SCCs don't align with the secCompProfile set on the pods, which result in the pods with the added secCompProfile failing to schedule / run.

Test plan for issue:

Unit tests + manual testing of 4.10 version

Testing instructions:

1. Create a 4.10 cluster at this aro operator version + RP version
2. Make sure MUO, aro-operator (worker and master), and geneva logging pods are working as intended.
3. Check the presence of: aro-worker and aro-master operators (secCompProfile), geneva logging namespace (should not have labels), and MUO deployment (secCompProfile)
4. Upgrade to 4.11
5. AdminUpdate the cluster
6. All the items in step 3 should have the appropriate things now

Changes

• Namespace:

	"pod-security.kubernetes.io/enforce": "privileged",
	"pod-security.kubernetes.io/audit":   "privileged",
	"pod-security.kubernetes.io/warn":    "privileged",

• Pods: under .spec.template.spec

      securityContext:
        runAsNonRoot: true
        seccompProfile:
          type: RuntimeDefault

• Pods: under .spec.template.spec.containers[]

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

Is there any documentation that needs to be updated for this PR?

nope

[bennerv]

/hold on testing - cc @SrinivasAtmakuri

[AldoFusterTurpin]

One concern about a possible panic and a couple of optional minor suggestions.
Thank you!

[jaitaiwan]

LGTM

[AldoFusterTurpin]

LGTM! Thanks for the minor tweaks.