Description:
When executing multiple warm migration plans with the following configuration:

5 plans, each migrating a single VM with 3 disks.
max_vms_inflight set to a value greater than 6.
Only two plans proceed with the full migration flow, as warm migration prioritizes total disk count over the number of VMs or plans. The remaining three plans are effectively waiting for disk slots to become available.

However, the UI inaccurately reflects all five plans as "Running," which could mislead users. Plans 3–5, which are not actively processing due to disk inflight limits, should be shown in a more appropriate state, such as "Waiting" or "Paused."

Attached is a screenshot illustrating the discrepancy:

1. Plan 1 and Plan 2 have begun the migration flow.
       Plans 3–5 remain inactive but are incorrectly labeled as "Running."
2. inside inactive plan in the example "plan3" but this plan appear as running 

This inconsistency in status representation creates confusion and should be corrected to accurately reflect the state of the plans.

Steps to Reproduce:

1. Setup Migration Environment:

• • Configure the migration tool with max_vm_inflight set to a value greater than the total number of disks per migration (e.g., >6).

1. Create Migration Plans:

• • Create and initiate 5 warm migration plans.
  • Each plan is responsible for migrating a single VM with 3 disks.

1. Observe Migration Status:

• • Monitor the status of each migration plan in the UI.

Expected Behavior:

• Active Plans: Only 2 migration plans should be actively running simultaneously (since 2 plans × 3 disks = 6 disks, which aligns with max_vm_inflight).
• Waiting Plans: The remaining 3 migration plans should be in a "Waiting" or "Paused" state, indicating they are queued and awaiting available disk slots.

Actual Behavior:

• All Plans Displayed as Running: The UI incorrectly shows all 5 migration plans as "Running."
• Inactive Plans: Only 2 plans are actively processing the migrations, while the other 3 are idle and waiting for disk slots to become available.
• Misleading Information: Users receive false confirmation that all migration plans are in progress, leading to confusion and potential mismanagement.

UPDATE : 
this bug is relevant for both cold/warm migration : 
In cold migration, i have set  max_vms_inflight to 2, as slots are allocated per VM rather than per disk. i ran plans 2 through 5, plans 2 and 3 started their migration flows as expected, but plans 4 and 5 were stalled due to the slot limitation.
Despite this, the UI still showed them as "Running," which doesn't align with their actual inactive status.