EKSA Plugin Upgrade to Cluster leaves one of the ETCD Machine in Provisioned state and Control Plane in Scaling State

**What happened**:
Applying anywhere plugin update (v0.16.5) to EKSA Cluster(vSphere) leaves one of the etcd machine in provisioned state and also has etcdadm cluster point to old etcd IPs.Similarly the CP points to the old etcd IPs and on few occassions has KubeadmControlplane in Scaling state .

**What you expected to happen**:
New ETCD Machines to be in running state and CP pointing to the new ETCD IPs.

**How to reproduce it (as minimally and precisely as possible)**:
NA

**Anything else we need to know?**:
Deleted etcd machines in provisioned state multiple times but still see the same issue.
Raised a support case but no luck with resolving the issue yet.

**Environment**:
- EKS Anywhere Release: v0.16.5
- EKS Distro Release:v1.24.12-eks-76dc719

No files, tests, entry points, or minimal reproduction are identified in the issue. Start by reproducing the v0.16.5 plugin upgrade on vSphere and inspect the etcd machines, etcdadm endpoints, and KubeadmControlPlane; done means replacement etcd machines reach running state and the control plane uses the new etcd IPs.

Written by the indexing model from the issue text.