Description of the issue{}

User has selected 5 security groups from "Add machine pool" dialog during machine pool creation. The inline backend error has thrown when user tried to create a machine pool. This seems confusing as UI allowed to create a machine pool with max limit of security group.

The Problem could be there was some non custom security groups are getting assigned to the machine pool that break the security group quota limits check together with custom security group added by the user. Ex: User select 5 security groups + 1 additional comes from backend? = 6 security group total but limit is 5. Hence we should consider the security group quota limitation dynamically from UI and create validation rule something similar to How the backend request  works now else this behavior from UI will be super confusing the user.

Steps to Reproduce:

1. Launch OCM UI staging.
2. Open ready ROSA Hypershift cluster (Make sure the VPC configured against cluster has more than 5 custom security group definitions).
3. Go to Machine pool tab.
4. Click "Add machine pool" button.
5. Fill all required fields, Go to security group sections.
6. Select 5 security group definition.
7. Click " Add machine pool" button and see the behavior.

Actual results:

At step 7, Unable to create machine pool with 5 security groups and it returns the quota limit error from backend. This confuses user as the max limit security group support is 5 and UI allowed to create the machine pool with 5 security group. 

Expected results:

To avoid the problem seen above, Introduce dynamic security group quota limit check and validate the UI accordingly.