restart claim sync when PVC is updated

[RomanBednar]

We should not rely on syncUnboundClaim() to do nothing after it updates PVC with a default storage class until next re-sync but instead restart the sync explicitly to make sure we hit isDelayBindingMode() and findBestMatchForClaim() immediately right after the PVC update.

What type of PR is this?

/kind bug

What this PR does / why we need it:

This PR is based on suggestion in this comment: https://github.com/kubernetes/kubernetes/pull/111467/files#r995755779

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[KEP]: https://github.com/kubernetes/enhancements/issues/3333

[k8s-ci-robot]

@RomanBednar: This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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/test-infra repository.

[RomanBednar]

/assign @liggitt

[liggitt]

/sig storage
/lgtm

[liggitt]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: liggitt, RomanBednar

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:

• pkg/controller/volume/persistentvolume/OWNERS [liggitt]

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