Bump kubernetes-sigs/cluster-api-provider-vsphere to latest release

UPSTREAM_PROJECTS.yaml

@@ -183,7 +183,7 @@ projects:
             go_version: "1.19"
       - name: cluster-api-provider-vsphere
         versions:
-          - tag: v1.10.0
+          - tag: v1.10.1
             go_version: "1.21"
       - name: cri-tools
         versions:

projects/kubernetes-sigs/cluster-api-provider-vsphere/ATTRIBUTION.txt

@@ -152,10 +152,10 @@ https://github.com/kubernetes/utils
 ** sigs.k8s.io/apiserver-network-proxy/konnectivity-client; version v0.28.0 --
 https://github.com/kubernetes-sigs/apiserver-network-proxy
 
-** sigs.k8s.io/cluster-api; version v1.7.1 --
+** sigs.k8s.io/cluster-api; version v1.7.3 --
 https://github.com/kubernetes-sigs/cluster-api
 
-** sigs.k8s.io/cluster-api-provider-vsphere; version v1.10.0 --
+** sigs.k8s.io/cluster-api-provider-vsphere; version v1.10.1 --
 https://github.com/kubernetes-sigs/cluster-api-provider-vsphere
 
 ** sigs.k8s.io/controller-runtime; version v0.17.3 --

projects/kubernetes-sigs/cluster-api-provider-vsphere/CHECKSUMS

@@ -1,2 +1,2 @@
-f6689d7e5d03c6126c14fdb506ca7f5f34631a69e40af7934a506da6a41a9d1a  _output/bin/cluster-api-provider-vsphere/linux-amd64/manager
-ade682ab1f1c4d67238bd90e54d482373ba4b37b97b7cf1c599370bae44138bd  _output/bin/cluster-api-provider-vsphere/linux-arm64/manager
+de14fcc845827b9a2976aab4c2f5207bb3db0df36245f1906582693451f09985  _output/bin/cluster-api-provider-vsphere/linux-amd64/manager
+467a559176fecf312cb04cfd2f436b3c70a8e5a2f95bb593d1b6df71384b8a3d  _output/bin/cluster-api-provider-vsphere/linux-arm64/manager

projects/kubernetes-sigs/cluster-api-provider-vsphere/GIT_TAG

@@ -1 +1 @@
-v1.10.0
+v1.10.1

projects/kubernetes-sigs/cluster-api-provider-vsphere/README.md

@@ -1,5 +1,5 @@
 ## **Cluster API Provider for vSphere**
-![Version](https://img.shields.io/badge/version-v1.10.0-blue)
+![Version](https://img.shields.io/badge/version-v1.10.1-blue)
 ![Build Status](https://codebuild.us-west-2.amazonaws.com/badges?uuid=eyJlbmNyeXB0ZWREYXRhIjoiYm85WnJ4aDc2ZXhhVUxOWHJuUFJwN3FlQmE2L1Q4b2ZzNG91OVpjNVNGM1ZvbVBEUUM2bkdER3N5eVNrWTBKS2VSSW9Oa051aFVWS1dzVVlTOHBBZ0NRPSIsIml2UGFyYW1ldGVyU3BlYyI6IlEwOWNtd0llNXdjUGRvQWkiLCJtYXRlcmlhbFNldFNlcmlhbCI6MX0%3D&branch=main)
 
 The [Cluster API Provider for vSphere (CAPV)](https://github.com/kubernetes-sigs/cluster-api-provider-vsphere) is a a concrete implementation of Cluster API for vSphere, which paves the way for true vSphere hybrid deployments of Kubernetes. CAPV is designed to allow customers to use their existing vSphere infrastructure, including vCenter credentials, VMs, templates, etc. for bootstrapping and creating workload clusters.
@@ -32,7 +32,7 @@ You can find the latest version of this image [on ECR Public Gallery](https://ga
    1. Run `git format-patch <commit>`, where `<commit>` is the last upstream commit on that tag. Move the generated patches under the patches/ folder in this repo.
 1. Update the `GIT_TAG` file to have the new desired version based on the upstream release tags.
 1. Compare the old tag to the new, looking specifically for Makefile changes.
-   ex: [1.7.0 compared to 1.7.4](https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/compare/v1.7.0...v1.10.0). Check if the [manifest-modification](https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/blob/27368586949f746c6830a47dc2439cd5ebe57dd2/Makefile#L568) or [release-manifests](https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/blob/27368586949f746c6830a47dc2439cd5ebe57dd2/Makefile#L577C9-L577C26)
+   ex: [1.7.0 compared to 1.7.4](https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/compare/v1.7.0...v1.10.1). Check if the [manifest-modification](https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/blob/27368586949f746c6830a47dc2439cd5ebe57dd2/Makefile#L568) or [release-manifests](https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/blob/27368586949f746c6830a47dc2439cd5ebe57dd2/Makefile#L577C9-L577C26)
    targets have changed in the Makefile, and make the required changes in create_manifests.sh
 1. Check the go.mod file to see if the golang version has changed when updating a version. Update the field `GOLANG_VERSION` in
    Makefile to match the version upstream.