Avoid double quota accounting if last CnsRegisterVolume CR instance status update for success fails

[akankshapanse]

What this PR does / why we need it:
Currently in static volume registeration via CnsRegisterVolume CR, the quota for the static PVC is managed by manually increasing "Reserved" field in associated SPU CR of that namespace & PVC type and then decreasing "Reserved" + increasing "Used" field with capacity to account quota for that PVC. After quota update is done, we mark reconcile as success in CnsRegisterVolume CR by updating status field.
However if the status update on CnsRegisterVolume CR fails, we retry the reconcile and quota gets accounted again in next reconcile cycle for same PVC object. To avoid this, we mark quota update error on CnsRegisterVolume CR and avoid quota update if already done in earlier run.

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:
Unit tests added to cover the scenario with help from cursor, will provide fix to reported, who has been seeing the issue frequently

Unit test log :

# $ go test ./pkg/syncer/cnsoperator/controller/cnsregistervolume/... -ginkgo.focus="updateQuotaInStoragePolicyUsageWithClient function tests" -v
=== RUN   TestCnsRegisterVolumeController
Running Suite: CnsRegisterVolumeController Suite - /home/pansea/csi-src/vsphere-csi-driver/pkg/syncer/cnsoperator/controller/cnsregistervolume
==============================================================================================================================================
Random Seed: 1764594652

Will run 6 of 35 specs

Ran 6 of 35 Specs in 0.004 seconds
SUCCESS! -- 6 Passed | 0 Failed | 0 Pending | 29 Skipped

Special notes for your reviewer:

Release note:

Avoid double quota accounting if last CnsRegisterVolume CR instance status update for success fails

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: akankshapanse

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [akankshapanse]

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