Customize the scc of deployments to make ocm run under different scc

[zhiweiyin318]

Describe the enhancement
currently the scc in the deployments can not be customized, the ocm may could not run under some restricted scc.
need an approach to solve ssc .

the related PRs :
#250
#252

[tamalsaha]

I was able to get things running under restricted security profile using the following chages.

• kluster-manager@a57ff0b
• kluster-manager/cluster-proxy@57a5ab2
• kluster-manager/managed-serviceaccount@41ff74b
• kluster-manager/installer@bea2c65#diff-e32133c32f6fa4d852347532435258c5c84df0c06c018e7eefa4da6b7bd1510b

By restricted profile, I mean pod-security.kubernetes.io/enforce: restricted label on namespaces.

namespaces=( \
  open-cluster-management \
  open-cluster-management-addon \
  open-cluster-management-agent \
  open-cluster-management-agent-addon \
  open-cluster-management-cluster-auth \
  open-cluster-management-cluster-proxy \
  open-cluster-management-hub \
)

for ns in ${namespaces[@]}; do
  kubectl create ns $ns
  kubectl label ns $ns pod-security.kubernetes.io/enforce=restricted
done

[github-actions]

This issue is stale because it has been open for 120 days with no activity. After 14 days of inactivity, it will be closed. Remove the stale label to prevent this issue from being closed.