Description of problem:

In Rosa or OSD wizard, when editing "max-nodes-total" value in 'Edit Cluster Autoscaling" dialog AND on cluster autoscaling modal on day 2, the max-nodes-total does not have valuation on the minimum allowed value. This allows user to enter invalid values.

How reproducible:
always

Steps to Reproduce:

1. Open OCM UI staging , go to cluster list.
2. Open a ROSA classic or an OSD ready cluster.
3. Go to machine pool tab and click "Edit cluster autoscaling settings".
4. Turn the autoscaler on.
5. In max-nodes-total field, try to enter "1".
6. See the behavior

Actual results:

An error is returned from backend and displayed to the user.

Expected results:

UI should introduce client side validation for the minimum allowed value. The logic to determine the min value is:

 
if osd: if ccs (customer cloud account): if single az:
maxNodesTotal minimum value = 2 worker nodes + 2 infra nodes + 3 master nodes if multi az:
maxNodesTotal minimum value = 3 worker nodes + 3 infra nodes + 3 master nodes if non-ccs (red hat account): if single az:
maxNodesTotal minimum value = 4 worker nodes + 2 infra nodes + 3 master nodes if multi az:
maxNodesTotal minimum value = 9 worker nodes + 3 infra nodes + 3 master nodesif rosa: if classic: (same as ccs above) if single az:
maxNodesTotal minimum value = 2 worker nodes + 2 infra nodes + 3 master nodes if multi az:
maxNodesTotal minimum value = 3 worker nodes + 3 infra nodes + 3 master nodes