Update vsphere provider template for creating capi objects using v1beta1 api

[mrajashree]

Update the templates under vsphere/config package to use v1beta1 apis for CAPI and CAPV.

• Update template for all CAPI CRDs. This includes Cluster, KubeadmControlPlane, ClusterResourceSet, KubeadmConfigTemplate, MachineDeployment and MachineHealthCheck. Updates include:

• Changing the apiversion to v1beta1

• Making API changes added between v1alpha3 and v1alpha4

• Making API changes added between v1alpha4 to v1beta1. There aren't any new changes between v1alpha4 and v1beta1, but refer the linked doc to confirm

• Update template for all CAPV CRDs. This includes VSphereCluster and VSphereMachineTemplate. Updates include:

• Changing the apiversion to v1beta1

• Making API changes added between v1alpha3 and v1alpha4. There is no official doc, refer v0.8.0 (v1alpha4) release notes. This is the main change:

  • The field .spec.CloudProviderConfiguration is removed from VSphereCluster spec. Cloud provider credentials and configuration details are now provided through ClusterResourceSet. It accepts a Secret ref for the vsphere credentials, and a configmap for vsphere configuration details and installing the CPI.
  • To get a sample template for reference, download clusterctl binary for v1beta1 version (from this capi release). Follow the quickstart guide selecting vsphere as the infrastructure provider to generate a sample cluster config.

• Check for any API changes between v1alpha4 and v1beta1. Refer the release notes.

• Since the EKS-anywhere code changes to start using v1beta1 APIs are not merged, and the tags for capi/capv aren't updated with patches, test cluster creation directly using cluster-api.

[mrajashree]

Closing as PR is merged #976