Replace update api invocations with patch api

[chethanv28]

What this PR does / why we need it:
Replace update api invocations with patch api for multiple api resources & for the following files:

PersistentVolumeClaim (annotations)	                               pkg/syncer/fullsync.go
PersistentVolumeClaim (finalizer)	                             pkg/syncer/fullsync.go
VolumeSnapshot (finalizer)	pkg/syncer/fullsync.go
PersistentVolumeClaim (health annotation)	pkg/syncer/volume_health.go
PersistentVolumeClaim (health annotation retry)	pkg/syncer/volume_health.go
PersistentVolumeClaim (backing disk annotation)	pkg/syncer/pv_to_backingdiskobjectid_mapping.go
PersistentVolumeClaim (backing disk annotation retry)	pkg/syncer/pv_to_backingdiskobjectid_mapping.go
StoragePool	pkg/syncer/storagepool/intended_state.go
CnsFileVolumeClient	pkg/syncer/metadatasyncer.go
CnsFileVolumeClient	pkg/internalapis/cnsoperator/cnsfilevolumeclient/cnsfilevolumeclient.go
CnsFileVolumeClient	pkg/internalapis/cnsoperator/cnsfilevolumeclient/cnsfilevolumeclient.go
CnsFileVolumeClient	pkg/internalapis/cnsoperator/cnsfilevolumeclient/cnsfilevolumeclient.go
CnsVolumeOperationRequest	pkg/internalapis/cnsvolumeoperationrequest/cnsvolumeoperationrequest.go
CnsRegisterVolume	pkg/syncer/cnsoperator/controller/cnsregistervolume/cnsregistervolume_controller.go
CnsUnregisterVolume	pkg/syncer/cnsoperator/controller/cnsunregistervolume/controller.go
CnsUnregisterVolume	pkg/syncer/cnsoperator/controller/cnsunregistervolume/controller.go
CnsNodeVmAttachment	pkg/syncer/cnsoperator/controller/cnsnodevmattachment/cnsnodevmattachment_controller.go
CnsNodeVmAttachment	pkg/syncer/cnsoperator/controller/cnsnodevmattachment/cnsnodevmattachment_controller.go
CnsNodeVMBatchAttachment Status	pkg/syncer/cnsoperator/controller/cnsnodevmbatchattachment/cnsnodevmbatchattachment_helper.go
PersistentVolume	pkg/kubernetes/kubernetes.go
PersistentVolumeClaim	pkg/kubernetes/kubernetes.go
PersistentVolumeClaim	pkg/kubernetes/kubernetes.go
ConfigMap	pkg/csi/service/common/commonco/k8sorchestrator/k8sorchestrator.go
PersistentVolume	pkg/csi/service/common/commonco/k8sorchestrator/k8sorchestrator.go
PersistentVolumeClaim	pkg/csi/service/common/commonco/k8sorchestrator/k8sorchestrator.go
PersistentVolumeClaim	pkg/csi/service/common/commonco/k8sorchestrator/k8sorchestrator_helper.go
CustomResourceDefinition	pkg/kubernetes/kubernetes.go
Generic Object (with finalizer)	pkg/kubernetes/kubernetes.go
Generic Object (remove finalizer)	pkg/kubernetes/kubernetes.go
Generic Object Status	pkg/kubernetes/kubernetes.go

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #

Testing done:
TBA

Special notes for your reviewer:

Release note:

Replace update api invocations with patch api

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chethanv28

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [chethanv28]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

@chethanv28: 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
pull-vsphere-csi-driver-verify-fmt	a6cc461	link	true	/test pull-vsphere-csi-driver-verify-fmt
pull-vsphere-csi-driver-verify-golangci-lint	a6cc461	link	true	/test pull-vsphere-csi-driver-verify-golangci-lint
pull-vsphere-csi-driver-unit-test	a6cc461	link	true	/test pull-vsphere-csi-driver-unit-test

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Details

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.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale