Subnet label values are not interpreted correctly by new scheduler

New hypershift scheduler is not replacing '.' with ',' in subnet label values, resulting in invalid subnet annotations for load balancer services. 

 4.16.0

 Always

    1. Using new hypershift request serving node scheduler, create a HostedCluster.
    2. Use nodes that are labeled with subnets separated by periods instead of commas.
    

    HostedCluster fails to roll out because router services are not deployed.

    HostedCluster provisions successfully.