Set SCC's RunAsUser as MustRunAsRange

Upstream Helm Chart is removing explicit `runAsUser` value from the
Deployment and DaemonSet resources. This practically means the UID
will be inherited from image's Dockerfile.

Users on vanilla Kubernetes clusters will not observe a change in
behavior, unless they have exotic configurations.

However, OpenShift does have additional security measures. It suggests
using randomized UIDs/GIDs for workloads. To enable this, the custom
Security Context Constraint resources are being updated.
The `MustRunAsRange` policy is utilized with pre-allocated values
(no explicit range min/max), which effectively allows OpenShift to
pick its own ranges.

resources/scc-daemonset.yaml

@@ -5,8 +5,7 @@ metadata:
   name: nginx-ingress-admin
 allowPrivilegedContainer: false
 runAsUser:
-  type: MustRunAs
-  uid: 101
+  type: MustRunAsRange
 seLinuxContext:
   type: MustRunAs
 fsGroup:

resources/scc.yaml

@@ -5,8 +5,7 @@ metadata:
   name: nginx-ingress-admin
 allowPrivilegedContainer: false
 runAsUser:
-  type: MustRunAs
-  uid: 101
+  type: MustRunAsRange
 seLinuxContext:
   type: MustRunAs
 fsGroup: