Make reason for Mig* resource unreadiness more obvious for MigPlan and MigMigration

[djwhatle]

Copied over from 1003 since this is a separate issue.

---

Problem

When Mig* resource goes unready, the reason for unreadiness isn't exposed. User has to dig through the related resources to find out what stopped the migration.

Suggested solution with MigPlan as example

If MigPlan status is unready, show specific problem e.g. "Plan is unready due to Replication Repo xyz being unready.", or equivalent warning for Clusters being unready. This can be accomplished by checking MigPlan for conditions

• SourceClusterNotReady
• DestinationClusterNotReady
• StorageNotReady

User should be pointed to this specific information instead of generic "Plan Unready" when this more specific info is available.

[djwhatle]

Full list of condition messages for migplan:
https://github.com/konveyor/mig-controller/blob/master/pkg/controller/migplan/validation.go#L29

Full list of condition messages for migmigration:
https://github.com/konveyor/mig-controller/blob/master/pkg/controller/migmigration/validation.go#L46