Description of problem:

In Hypershift ROSA cluster, minimum node count/replica is two from node pool/machine pools. Currently quick delete actions in UI over machine pool set  keeps the minimum node count value less than 2 in Hypershift clusters. This is wrong and we need to restrict the user doing /performing this action.

Steps to reproduce:

1. Install ROSA hypershift cluster via CLI .
2. Once installation is successful, Create two additional machine pools (say the name as worker-1,worker-2) with replicas 1.
3. Launch OCM UI staging.
4. Navigate to machine pools tab.
5. Perform quick delete action one after another against machine pools ( for ex: worker and worker-1)
6. View the behavior.

Actual results:
Before performing Step 5 action, There are three machine pools in cluster i.e. worker with 2 replicas, worker-1 with 1 replicas and worker-2 with 1 replicas.
After quick delete action on  worker and worker-1 machine pools, the cluster remained with worker-2 i.e. it has only 1 replica or node.
The error message i.e. Cluster should have minimum of 2 replicas  wasn't shown in UI during this action.
This violates the ROSA Hypershift machine pool requirement i.e. minimum 2 replicas or nodes under nodepool or machine pool.
Note: This issue could be , user performs actions quickly and some reason validation is  suppressed user's action.

Expected results:
User should not be allowed to delete machine pools when the total replica or node count is <2 for hypershift cluster under any circumstance.
Refer attached screen recordings MachinePoolsdelete.mp4