🐛 vspherevm: ensure that the cache gets updated when patching .status.taskRef

[chrischdi]

What this PR does / why we need it:

A vSphereVM could reconcile again with using an outdated object from the cache.

In case of a VSphereVM which get's deleted this could lead to triggering a task to destroy the VM twice. While the second one would fail after some timeout.

Did hit this issue at https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_cluster-api-provider-vsphere/2594/pull-cluster-api-provider-vsphere-e2e-main/1752293260056858624

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

[chrischdi]

/assign sbueringer

[codecov]

Codecov Report

Attention: 9 lines in your changes are missing coverage. Please review.

Comparison is base (036fb05) 64.70% compared to head (22bb16e) 64.66%.
Report is 5 commits behind head on main.

Files	Patch %	Lines
controllers/vspherevm_controller.go	10.00%	8 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2677      +/-   ##
==========================================
- Coverage   64.70%   64.66%   -0.04%     
==========================================
  Files         118      118              
  Lines        8580     8593      +13     
==========================================
+ Hits         5552     5557       +5     
- Misses       2597     2604       +7     
- Partials      431      432       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[sbueringer]

/test pull-cluster-api-provider-vsphere-e2e-main

[chrischdi]

/test pull-cluster-api-provider-vsphere-e2e-main

[sbueringer]

Thx!

/lgtm
/approve

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 7993113a00192c54ba542f6b1ca58deac309866b

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sbueringer

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 [sbueringer]

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

[sbueringer]

/retest

[chrischdi]

/cherry-pick release-1.9

[k8s-infra-cherrypick-robot]

@chrischdi: new pull request created: #2680

In response to this:

/cherry-pick release-1.9

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.