CMP-3915: Update SCC variable to include new SCCs for 4.20

[rhmdnd]

4.20 ships with two new SCCs that allow additional capabilities. Let's
add them to the variable so we don't get false positives on scans
running on OCP 4.20.

[Vincent056]

/lgtm

[Anna-Koudelkova]

Premerge verification passed on OCP 4.20 + CO 1.8.0. + content built from this PR 14104:

1. Create ssb:

$ oc compliance bind -N ocp4 profile/ocp4-cis
Creating ScanSettingBinding ocp4
$ oc compliance bind -N upstream profile/upstream-ocp4-cis
Creating ScanSettingBinding upstream

2. Wait for the scans to finish and check the results:

$ oc get suite 
NAME       PHASE   RESULT
ocp4       DONE    NON-COMPLIANT
upstream   DONE    NON-COMPLIANT

$ oc get ccr |grep scc-limit-container-allowed-capabilities
ocp4-cis-scc-limit-container-allowed-capabilities                          FAIL     medium
upstream-ocp4-cis-scc-limit-container-allowed-capabilities                 PASS     medium

3. Check the variable values:

$ oc get variable ocp4-var-sccs-with-allowed-capabilities-regex -ojsonpath='{.value}' -n openshift-compliance
^privileged$|^hostnetwork-v2$|^restricted-v2$|^nonroot-v2$|^insights-runtime-extractor-scc$

$ oc get variable upstream-ocp4-var-sccs-with-allowed-capabilities-regex -ojsonpath='{.value}' -n openshift-compliance
^privileged$|^hostnetwork-v2$|^restricted-v2$|^restricted-v3$|^nonroot-v2$|^insights-runtime-extractor-scc|^nested-container$

[Anna-Koudelkova]

/lgtm

[openshift-ci]

@rhmdnd: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-aws-openshift-platform-compliance	ef522d8	link	true	/test e2e-aws-openshift-platform-compliance
ci/prow/e2e-aws-openshift-node-compliance	ef522d8	link	true	/test e2e-aws-openshift-node-compliance

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.