Current behavior:

• The user can edit the settings fields under the plan details tab (e.g. Warm migration, Target namespace etc) for all plan statuses, including for running, archived, not ready and succeeded plans.
• The user can edit hooks under hooks tab for archived and running plans.
• The user can edit mappings under mappings tab for archived (never started) plans.
• the user can remove VMs under VMs tab for archived plans

Those use cases are invalid and might cause strange behaviors, for example, editing the  warm migration settings for a running plan might stop the plan's migration and change the status to canceled.

Expected {}behavior:

Editing a plan should be enabled for the following statuses only:
'Unknown', 'Canceled', 'Error', 'Failed', 'vmError', 'Warning',
'Ready

and disabled for all others

The user can't remove VMs for an archived plans.