Custom SCC can break oauth if priority is 10 or higher

Issue

• After creating a custom SCC with priority 10 or higher, authentication stays degraded during upgrades until custom scc is removed.
• After creating a custom SCC with priority 10 or higher, whenever an oauth pod in openshift-authentication is deleted and a new one is spawned, the new pod stays in CreateContainerConfigError and won't start.