UI erroneously reported migration completed when VM did not exist in PCD

[jeremymv2]

Issue:
During a migration of a large batch of VMs, the vJailbreak PODs exhausted the host resources and were evicted/killed from the K3s cluster. This left the migration status in the UI erroneously reporting some VMs had been migrated successfully. The VMs in question did not exist in PCD. This gave the user a very low level of confidence in the tool.

We should prevent this from happening by accurately reflecting migration status and leveraging the PCD API to determine if the VM is indeed instantiated and what its running state is.

[patil-pratik-87]

@OmkarDeshpande7 is assigning this to you, as the backend is probably sending an incorrect status.

[jeremymv2]

@patil-pratik-87 before we pass this off to the backend, I want to ensure you have ruled out any way in which the front end could have marked the migration completed without have explicitly received that detail from the backend.

The scenario when this occurred was when the vJailbreak VM had exhausted resources and the K3s cluster had evicted many of the PODs. The PODS were therefore in a disfunctional state. In this scenario, is it possible that the frontend could have erroneously defaulted to completed status if the actual state was undetectable?

[patil-pratik-87]

@jeremymv2 I was able to reproduce this, the backend is sending the wrong status(Succeeded) on the Migration object, even though the VM is not present on PCD.
Attaching the screenshots.

@OmkarDeshpande7 can you take a look at it?