[MTV-1880] Move 'Plan name' field to step 1 of create migration plan wizard

[jpuzz0]

📝 Links

MTV-1880
Design JIRA: https://issues.redhat.com/browse/HPUX-259

📝 Description

Moves "Plan name" form field of the create migration plan wizard to step 1 and enforces user to enter a value before proceeding to step 2.

Also, when creating from a provider's details page within the "Virtual machines" tab, clicking "Create migration plan" navigates users to step 1 (where a plan name must be entered) instead of step 2.

🎥 Demo

From list page:
https://github.com/user-attachments/assets/f8383824-34d2-45c6-91c8-7c071edbc9ab

From provider details page:
https://github.com/user-attachments/assets/3e1bea8f-4ee9-4db4-93b5-6471497cfeec

📝 CC:

@mmenestr

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 36.20%. Comparing base (13484d0) to head (6aee340).
Report is 184 commits behind head on main.

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1436      +/-   ##
==========================================
- Coverage   36.81%   36.20%   -0.62%     
==========================================
  Files         158      159       +1     
  Lines        2548     2580      +32     
  Branches      599      602       +3     
==========================================
- Hits          938      934       -4     
- Misses       1428     1631     +203     
+ Partials      182       15     -167     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[metalice]

can u please create a func in a util file for that?

[sgratch]

@mmenestr @jpuzz0
A concern regarding this design of always navigating to Wizard's step 1 (will add this to the Jira ticket as well):
If the user selected few VMs from different pages within the provider's VMs list, then in previous implementation he was navigated to Wizard's step 2 where the Selected VMs number field is displayed. If the wanted to change vms selection, he had to go back to step 1 and navigate to the relevant VM's page for changing.

Now in the new design, the user is navigated directly to step 1, where he can't even see that his selections were applied (if done on page > 1) and no Selected VMs field is shown

So either we need to move the Selected VMs number field to step 1 as well, or navigate the user to the 1st VMs page where VMs are pre--selected.
WDYT?

[metalice]

@mmenestr @jpuzz0 A concern regarding this design of always navigating to Wizard's step 1 (will add this to the Jira ticket as well): If the user selected few VMs from different pages within the provider's VMs list, then in previous implementation he was navigated to Wizard's step 2 where the Selected VMs number field is displayed. If the wanted to change vms selection, he had to go back to step 1 and navigate to the relevant VM's page for changing.

Now in the new design, the user is navigated directly to step 1, where he can't even see that his selections were applied (if done on page > 1) and no Selected VMs field is shown

So either we need to move the Selected VMs number field to step 1 as well, or navigate the user to the 1st VMs page where VMs are pre--selected. WDYT?

If the number in question of total VM is important to display to user I would go and move it to the description of the action.
Which means, Create Plan button will have a description below with the {vmsList.length}