Description of the issue
User has installed an OSD cluster with version <4.15.0 and custom VPC (having  some security groups). As part of day 2 action, user has tried to add a new machine pool with security group  definition but this blocks from UI with wrong message as below. This is also seen with "Edit machine pool" dialog as well.

See recording attached SecurityGroupOSDDay2BlockerIssue.mp4

Steps to Reproduce:

1. Launch OCM UI staging.
2. Open ready OSD cluster (Make sure the VPC configured against cluster has 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. Tried to add security groups and see the behavior.

Actual results:

At step 6, The "Add machine pool" dialog indicated that "To use security group, your cluster must be version 4.15.0 or newer". This blocks user from creating machine pool with security groups. This wrong from OSD cluster type perspective as it support lower versions ex: 4.14. This is critical side effect of recent Hypershift Security group.

Expected results:

Both OSD and ROSA cluster should allow user to add machine pool with security group definition in case the cluster version is lower than 4.15 i.e. in this case 4.14.x