Bump VM operator to the next release

[fabriziopandini]

A few notes for the next bump:

•  VM Operator is going to stop pulling in the topology CRDs into the manifest, we should pull them in from
  • https://github.com/vmware-tanzu/vm-operator/blob/main/config/crd/external--crds/topology.tanzu.vmware.com_availabilityzones.yaml
  • https://github.com/vmware-tanzu/vm-operator/blob/main/config/crd/external-crds/topology.tanzu.vmware.com_vspherezones.yaml
• Zones
  • Use Zone CRD directly from vm-operator and get rid of our copy
  • Extend e2e test coverage to test both zone variants

[sbueringer]

@fabriziopandini Q: is this something that we should do now? If not, how do we know when to do it? (or just on the next tag/release of vm-operator?)

[fabriziopandini]

AFAIK there is no public calendar we can rely on, but at this point I assume this should not happen before CAPV 1.11
I'm trying to keep an eye on it, for now it is a sort of self memo about something popped up in an internal slack thread

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 issue is closed

You can:

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

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

/lifecycle stale