Update OpenShift security context constraints to support the operator service account

[jvoravong]

Description:

• Bug Fix: Addressed an issue where the Operator was not always deployable to OpenShift environments due to the lack of a validating Security Context Constraint.
• Updates:
  • Enhanced Security Context Constraints (SCC) for OpenShift to fix formatting issues and include support for the operator service account.
  • Changed the SCC fsGroup type from MustRunAs to RunAsAny to avoid issues with dynamic default fsGroup constraint value ranges, which could prevent the operator from deploying in OpenShift environments. Users can still override SCC settings using the securityContextConstraintsOverwrite value.
  • Refer to the OpenShift documentation for details: OpenShift SCC Strategies
    • FSGroup - MustRunAs - Requires at least one range to be specified if not using pre-allocated values. Uses the minimum value of the first range as the default. Validates against the first ID in the first range.

Testing:

• Reproduced the bug and tested the fix with OpenShift 4.12.11 (Kubernetes v1.25.7) to ensure successful deployment of the Operator. Testing other OpenShift versions as well.

[jvoravong]

The functional tests are failing with the current main branch, looking into fixing them.