e2e: Test replace cluster flow

[nirs]

When replacing a cluster we do:

1. Failover all apps to secondary cluster
2. Delete the dr cluster on for the failed cluster
3. Disable protecting for all apps
4. Take down the failed cluster (e.g. delete the vm)
5. Create a new cluster, deploying all the components on a standard managed cluster
6. Configure the new cluster on the hub (add dr cluster, update dr policy)
7. Enable dr for all applications
8. Relocate to the new cluster

Steps 4-5 are complicated and slow, so we can simulate them by pausing and resuming the same vm for much quicker. This is good enough for testing ramen flows.

[ShyamsundarR]

@nirs envtests for disable are also pending, are you tracking them with this or separately?

[nirs]

@nirs envtests for disable are also pending, are you tracking them with this or separately?

We added lot of tests for disable dr recently for handling invalid vr. Maybe open and issue for the missing tests?

[ShyamsundarR]

@nirs envtests for disable are also pending, are you tracking them with this or separately?

We added lot of tests for disable dr recently for handling invalid vr. Maybe open and issue for the missing tests?

Can you point to the PR? Is it testing deleted DRCluster and related DRPC reconciliation from a disable workflow at the hub?