change for operator and driver image sha

[hemalathagajendran]

Pull request checklist

Please check the type of change your PR introduces:

• [ ] Bugfix
• [ ] Feature Enhancement
• [ ] Test Automation
• [ ] Code Refactoring (no functional changes, no api changes)
• [x] Build related changes
• [ ] Community Operator listing
• [ ] Other (please describe):

How risky is this change?

• [x] Small, isolated change
• [ ] Medium, requires regression testing
• [ ] Large, requires functional and regression testing

[yorchpave]

hi @hemalathagajendran @Jainbrt

trying to look up the new digests in quay, looks like they are not present in the registry...if I try to pull the new operator sha from this PR:

[root@api.scale-cnsa-images-svl.cp.fyre.ibm.com ~]# podman pull quay.io/ibm-spectrum-scale/ibm-spectrum-scale-csi-operator@sha256:ef5a8058cf1decd53666ae0eadcb9d676a1597553e5c2e161d662bab73b1d011
Trying to pull quay.io/ibm-spectrum-scale/ibm-spectrum-scale-csi-operator@sha256:ef5a8058cf1decd53666ae0eadcb9d676a1597553e5c2e161d662bab73b1d011...
Error: initializing source docker://quay.io/ibm-spectrum-scale/ibm-spectrum-scale-csi-operator@sha256:ef5a8058cf1decd53666ae0eadcb9d676a1597553e5c2e161d662bab73b1d011: reading manifest sha256:ef5a8058cf1decd53666ae0eadcb9d676a1597553e5c2e161d662bab73b1d011 in quay.io/ibm-spectrum-scale/ibm-spectrum-scale-csi-operator: manifest unknown

Also, I realized that kustomization.yamL from overlays/cnsa was not updated with new digests, which is needed for us to pick up the new shas and update them in scale-core repo.

FYI this also applies for 2.11.1 changes