Description of problem:
In ROSA hypershift wizard flow, under machine pool step, the minimum and maximum  node count per machine pool validation seems broken when it exceed the cluster node count limit. See details below.
1. Minimum and maximum node count per machine pool could be edited till 180 irrespective of number of machine pool added. This is wrong because the limit of total number of node count is 180 per cluster and calculation should be based on the number of machine pools X node node count value. 

2. No validation in place if the total node count >180 (in this case it is 3 * 180 = 540).

How reproducible:

 Always

Steps to reproduce:

1. Launch OCM Staging.
2. Open ROSA wizard and select control plane type as "Hosted".
3. Reach to machine pool step by  providing all required values in each step.
4. Select VPC and add three machine pool sets.
5. Enable autoscaling checkbox.
6. Edit and enter the minimum and maximum node per machine pool as 180.
7. View the validations.
8. Proceed to next steps and reach to "Review and create" page.
9. Review the definition of compute node count.

Actual results:

 minimum and maximum node per machine pool accepted the value 180 irrespective of machine pools available. It is wrong.

Expected results:

 minimum and maximum node per machine pool  calculation and validation should be based on  the number of  machine pool count vs overall node count value. There should be proper validation when overall node count (autoscaling or not) > 180 from wizard.