Description of problem:

The TestRollingUpdate e2e test fails when checking for the updated instance types on all AWS machines when updating to CAPI v1.11:

nodepool_rolling_upgrade_test.go:120: Successfully waited for NodePool e2e-clusters-n24l8/node-pool-brllr-test-rolling-upgrade to finish the rolling upgrade in 6m33.125s
    nodepool_rolling_upgrade_test.go:143: 
        Expected
            <string>: m5.large
        to equal
            <string>: m5.xlarge

The test checks the InstanceType on old AWS machines that are still being deleted despite waiting for the nodepool to finish the upgrade.

Version-Release number of selected component (if applicable):

CAPA v2.10.0 / CAPI v1.11

How reproducible:

Always

Steps to Reproduce:
1. Build Hypershift and the Hypershift operator with CAPI 1.11 from the bump PR.
2. Install hypershift using the new operator image in a management cluster.
3. Run the TestNodePool/HostedCluster0/Main/TestRollingUpgrade e2e test on the management cluster with the CAPI 1.11 operator.

Actual results:

The MachineDeploymentComplete function returns true despite old machines still not deleted.

Expected results:

The MachineDeploymentComplete function should return true only when old machines are completely removed as it behaves in CAPI v1.10