Check for status of upgrade/delete instead of have sleeps in E2E

We should be checking for the status here on whether we can perform the next action or not, whether it is a prevalidation in the delete command or a status check in the e2e tests. That way we can remove our reliance on these arbitrary 5 min sleeps.

https://github.com/aws/eks-anywhere/blob/main/test/e2e/multicluster.go#L22

Start at test/e2e/multicluster.go#L22 and inspect the upgrade and delete flows that currently rely on five-minute sleeps. Trace the available status or prevalidation checks before each next action. Done means the E2E flow waits on status rather than arbitrary sleeps and still verifies the upgrade and delete operations.

Written by the indexing model from the issue text.