Error manually scaling vsphere worker nodes using latest EKSA

**What happened**:
Ran the below script to increase worker nodes from 1 to 3 nodes
```shell
eksctl anywhere upgrade cluster -f eksa/stg-ne-eks.yaml --kubeconfig stg-ne/stg-ne-eks-a-cluster.kubeconfig
Warning: VSphereDatacenterConfig configured in insecure mode
Performing setup and validations
Warning: VSphereDatacenterConfig configured in insecure mode
✅ Connected to server
✅ Authenticated to vSphere
✅ Datacenter validated
✅ Network validated
✅ Datastore validated
✅ Folder validated
✅ Resource pool validated
✅ Datastore validated
✅ Folder validated
✅ Resource pool validated
✅ Datastore validated
✅ Folder validated
✅ Resource pool validated
✅ Machine config tags validated
✅ Control plane and Workload templates validated
✅ Vsphere provider validation
✅ Validate OS is compatible with registry mirror configuration
✅ Validate certificate for registry mirror
✅ Control plane ready
✅ Worker nodes ready
✅ Nodes ready
✅ Cluster CRDs ready
✅ Cluster object present on workload cluster
✅ Upgrade cluster kubernetes version increment
✅ Validate authentication for git provider
✅ Validate immutable fields
Ensuring etcd CAPI providers exist on management cluster before upgrade
Pausing EKS-A cluster controller reconcile
Pausing GitOps cluster resources reconcile
Upgrading core components
Upgrading workload cluster
collecting cluster diagnostics
collecting management cluster diagnostics
collecting workload cluster diagnostics
⏳ Collecting support bundle from cluster, this can take a while {"cluster": "stg-ne", "bundle": "stg-ne/generated/stg-ne-2023-04-25T21:40:42Z-bundle.yaml", "since": 1682448042771430226, "kubeconfig": "stg-ne/stg-ne-eks-a-cluster.kubeconfig"}
Support bundle archive created {"path": "support-bundle-2023-04-25T21_40_43.tar.gz"}
Analyzing support bundle {"bundle": "stg-ne/generated/stg-ne-2023-04-25T21:40:42Z-bundle.yaml", "archive": "support-bundle-2023-04-25T21_40_43.tar.gz"}
Analysis output generated {"path": "stg-ne/generated/stg-ne-2023-04-25T21:41:32Z-analysis.yaml"}
Error: failed to upgrade cluster: applying capi control plane spec: executing apply: The kubeadmcontrolplanes "stg-ne" is invalid: metadata.resourceVersion: Invalid value: 0x0: must be specified for an update
```

I actually upgraded this cluster to latest control plane last week.

**What you expected to happen**:
Cluster scales up

**How to reproduce it (as minimally and precisely as possible)**:
Cluster is already running EKSA v0.15.2. Increase worker node count and rerun upgrade.

**Anything else we need to know?**:

**Environment**:
- EKS Anywhere Release: v0.15.2
- EKS Distro Release: 0.137.0

Start with the `eksctl anywhere upgrade cluster` command using `eksa/stg-ne-eks.yaml` and the `stg-ne/stg-ne-eks-a-cluster.kubeconfig` entry points, then inspect the upgrade path that applies the CAPI control plane spec. Reproduce the worker-node increase from one to three nodes on EKS Anywhere v0.15.2 and use the reported resourceVersion error as the failure condition; done means the cluster scales successfully.

Written by the indexing model from the issue text.