eksctl anywhere upgrade cluster fails to feed with the extra machines in hardware.csv

**What happened**:
I create an EKSA bare metal cluster with 1 CP node only.

Then I try to scale up with command "eksctl anywhere upgrade ..." with new hardware.csv which contains 2 new machines.

```
diff hardware-mgmt02.csv hardware-mgmt02-cp2.csv
2a3,4
> eksa-control-02,...,type=cp,/dev/sda
> eksa-control-03,...,type=cp,/dev/sda

eksctl anywhere upgrade cluster -f eksa-mgmt02-md-cluster.yaml --hardware-csv hardware-mgmt02-cp3.csv --no-timeouts -v 9
...
2024-04-15T08:21:06.065Z V0 🎉 Cluster upgraded!
...
```

After upgrade command succeeds, I try to run commands like:
kubectl get hardware -o wide -A

It only reports 1 machine (the original one):

```
kubectl get hardware -o wide -A
NAMESPACE NAME STATE
eksa-system eksa-control-01
```

**What you expected to happen**: I will see the new machines in the hardware list

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

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

**Environment**: ubuntu 20.04.06 LTS
- EKS Anywhere Release: V0.18.7
- EKS Distro Release: 1.26

Start by reproducing the reported `eksctl anywhere upgrade cluster` command with the two hardware CSV files and inspect the resulting `kubectl get hardware -o wide -A` output. Trace why the additional machines in `hardware-mgmt02-cp3.csv` are not represented after the upgrade; done means the new machines appear in the hardware list.

Written by the indexing model from the issue text.