PWX-30291: Removing sts and deployments from stork webhook

[pp511]

What type of PR is this?

bug

What this PR does / why we need it:
Remove Stork as the scheduler from Statefulsets and Deployments.

Currently we are not able to set Stork as the scheduler for Statefulsets because we rely on the PVC to be owned by Portworx. STS uses volumeClaimTemplates where PVC is not created when the webhook admission request comes to stork and schedulerName is not updated. Later when webhook admission request arrives for Pods, Stork does update the Schedulername and it works.

I believe there is no reason to update Stork as the scheduler for StatefulSets and Deployments when we have the webhook enabled for Pods. This PR is removing these webhook for Deployments and Statefulsets.

Please note that any annotation set on the Deployment or STS is not passed onto the Pods. To be able to specify stork.libopenstorage.org/disable-admission-controller that disables webhook for the specific STS /Deployment, we need to update it on spec.templace.metadata.annotations.

Does this PR change a user-facing CRD or CLI?:
no

Is a release note needed?:

Issue: Webhook errors observed when trying to mutate statefulsets to update Stork as the scheduler.
User Impact: Customers can not understand this error and gets the impression that Stork webhook is not working
Resolution: Removing wtbhookd for statefulsets and deployments as Stork already has a webhook for Pods that manages setting Stork as the default scheduler.

Does this change need to be cherry-picked to a release branch?:
yes 23.5

[cnbu-jenkins]

Can one of the admins verify this patch?

[adityadani]

looks good - make sure to test upgrades

[pp511]

MutatingWebhookConfiguration does get updated with the new config with this change. Will make sure to ask system test teams to test Stork upgrades as well.