Update Cluster API IPAM version from v1alpha1 to v1beta1 in CAPV

[PavanNeerudu]

What steps did you take and what happened:
While working with the CAPV, I noticed that the IPAM version used is still v1alpha1. This is despite the fact that the IPAM types have been promoted to v1beta1 in the cluster-api. Additionally, the first release of the Cluster API IPAM provider in-cluster uses v1beta1, leading to an inconsistency in the versions used.

What did you expect to happen:
NA

Anything else you would like to add:
Thought it would be beneficial to align the versions used in CAPV with the promoted IPAM types in the cluster-api and the CAPI IPAM provider in-cluster.

Environment:

• Cluster-api-provider-vsphere version:
• Kubernetes version: (use kubectl version):
• OS (e.g. from /etc/os-release):

[chrischdi]

/triage accepted