Tie SCC lifecycle with KataConfig

[bpradipt]

Fixes: KATA-1569

- Description of the problem which is fixed/What is the use case
The custom SCC created by the operator doesn't get deleted on the removal of KataConfig
@gkurz attempted to fix the issue in the following PR #191.
However, triggered by the suggestion from @littlejawa, we felt its logical to align the SCC lifecycle with the KataConfig lifecycle in further discussions. There is no reason to keep the SCC handling separated since kata-monitor pods use the custom SCC, and kata-monitor pods get created only after KataConfig creation. Thanks to @littlejawa and @gkurz for forcing us to relook at the issue which resulted in this PR. With this PR, the SCC gets created on KataConfig creation and cleaned up on deletion of the KataConfig.

- What I did
Changed how SCC gets created and deleted

- How to verify it

Check whether the customer SCC gets deleted after KataConfig deletion

- Description for the changelog

Tie SCC lifecycle with KataConfig

[bpradipt]

/assign @gkurz

[openshift-ci]

@bpradipt: GitHub didn't allow me to assign the following users: gkurz.

Note that only openshift members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @gkurz

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/test-infra repository.

[gkurz]

I'm skipping the test case commit as I don't really have the knowledge to review. Rest looks good.

[bpradipt]

/retest

[gkurz]

LGTM. Thanks @bpradipt !

[gkurz]

@bpradipt: 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/4.9-sandboxed-containers-operator-e2e 7ef52bc link false /test 4.9-sandboxed-containers-operator-e2e
ci/prow/sandboxed-containers-operator-e2e 7ef52bc link false /test sandboxed-containers-operator-e2e

Full PR test history. Your PR dashboard.

The tests seems to be failing because of infra problems, not related to the changes in this PR.

[bpradipt]

/retest

[bpradipt]

/retest

[bpradipt]

/retest

[bpradipt]

/retest

[gkurz]

/retest

[bpradipt]

last try
/retest

[openshift-ci]

@bpradipt: The following test 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/sandboxed-containers-operator-e2e	7ef52bc	link	false	/test sandboxed-containers-operator-e2e

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/test-infra repository. I understand the commands that are listed here.