Inefficient use of SG rules when creating Service LBs leads to scale issues

Each LB created for a Service type LoadBalancer results in 1 client rule and <# of public subnets> health rules being created.  The rules per SG quota in AWS is quite small; 60 by default, and 200 hard max.  OCP has about 40 rules OOTB. Assuming an HA cluster in 3 AZs, that is 4 rules per LB.  With default AWS quota, only ~5 LBs can be create and with the hard max of 200, only ~40 LBs can be created.

4.12

Always

1.  Create Service type LoadBalancer and observe increase in master-sg and worker-sg rules sets
2.
3.

4 rules are created

1 rules is created when the client rule is a superset of the per-subnet health rules

This ~4x the number of Services of type LoadBalancer.  This is required for Hypershift.