Currently, intra-cluster state migrations are possible. Since we are re-using the Final migration flow, it is possible that users may use Final migration post a successful state migration. After initial code review, we identified some corner cases that may result into unexpected outcomes when a Final migration is run after a state migration within the same cluster. We want to add validations for such cases so that the unexpected states can be automatically identified prior to running an intra-cluster migration. 

Some of the validations/warnings that we identified as high priority (all cases apply to intra-cluster only):
 
1. Migrating from NS A -> NS B:
    a. If NS B already exists, check if the UID/GID ranges match and raise a Warning on MigPlan if they do not
 2. Migrating from NS A -> NS A:
    a. Disable Final migration (migrating Kubernetes resources)
    b. Disable Stage migration 
    c. PVC names "must" be distinct