fix(Helm/operator): add REDHAT_CERTIFIED_OP=yes when deploying in Openshift cluster

[SD-13]

Purpose of PR?:

Fixes part of #2743, fixes Kubearmor installation on Openshift cluster using Helm chart

Does this PR introduce a breaking change?

If the changes in this PR are manually verified, list down the scenarios covered::

1. Applied the kubearmor helm chart

…/deployments/helm ❯ helm install kubearmor-operator ./KubeArmorOperator -n kubearmor --create-namespace

3. Created sample kubearmorConfig

❯ kubectl apply -f https://raw.githubusercontent.com/kubearmor/KubeArmor/main/pkg/KubeArmorOperator/config/samples/sample-config.yml

5. Tested with a 7-node OpenShift cluster with 2 worker nodes, so after snitch was completed, kubearmor daemonsets were created in the respective worker nodes

With the fix

❯ k get po -n kubearmor
NAME                                    READY   STATUS      RESTARTS   AGE
kubearmor-bpf-cri-o-47653-55jht         1/1     Running     0          18s
kubearmor-bpf-cri-o-47653-swrh2         1/1     Running     0          18s
kubearmor-controller-69f896fc94-kvjbh   0/1     Running     0          8s
kubearmor-controller-8577fb847-xwstx    1/1     Running     0          18s
kubearmor-operator-6d499d5959-86d6v     1/1     Running     0          3m27s
kubearmor-relay-558f89b75d-4bgjq        1/1     Running     0          25s
kubearmor-snitch-42kjh-gxsmv            0/1     Completed   1          15s
kubearmor-snitch-b9vgj-nw6vk            0/1     Completed   1          17s
kubearmor-snitch-d6n9j-kp5h8            0/1     Completed   1          18s
kubearmor-snitch-jgbdb-87kh4            0/1     Completed   1          17s
kubearmor-snitch-rgrz8-74l7s            0/1     Completed   1          16s
kubearmor-snitch-whwlw-xz75b            0/1     Completed   1          19s
kubearmor-snitch-zmldq-7dqsw            0/1     Completed   1          19s

Without the fix

✗ k get po -n kubearmor
NAME                                   READY   STATUS             RESTARTS      AGE
kubearmor-controller-8577fb847-4985b   0/1     Running            0             3s
kubearmor-operator-7f55445d89-qsxzw    1/1     Running            0             20s
kubearmor-relay-558f89b75d-cf7ww       1/1     Running            0             9s
kubearmor-snitch-2vzkz-rxwrl           0/1     CrashLoopBackOff   1 (10s ago)   11s
kubearmor-snitch-5hhfd-897jw           0/1     CrashLoopBackOff   1 (8s ago)    9s
kubearmor-snitch-c2vtf-zn9th           0/1     CrashLoopBackOff   1 (9s ago)    10s
kubearmor-snitch-qppvd-gbprd           0/1     CrashLoopBackOff   1 (7s ago)    8s
kubearmor-snitch-rg47j-d4gt2           0/1     CrashLoopBackOff   1 (10s ago)   11s
kubearmor-snitch-rhjx2-q7pcn           0/1     CrashLoopBackOff   1 (8s ago)    10s
kubearmor-snitch-rxlj7-v8n96           0/1     CrashLoopBackOff   1 (7s ago)    8s

Additional information for reviewer? :
After going through this OKD API list config.openshift.io/v1 was chosen as a reliable option.

Checklist:

• Bug fix. Fixes #
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• PR Title follows the convention of <type>(<scope>): <subject>
• Commit has unit tests
• Commit has integration tests

[AryanBakliwal]

@SD-13 although it works, can we try to check using a different way, wdyt?

[SD-13]

@AryanBakliwal I already tested the changes in an Openshift cluster and a local k3s cluster, it worked as expected. Let me attach the proof of concept for both tomorrow.
I can't think of any other way to test, please let me know if you have any suggestions. Thanks!

[SD-13]

@AryanBakliwal I went through the OKD API list and found config.openshift.io/v1 as a more reliable option.