For Product Offerings Connections, provide visibility of on-ramps

GET /product-offerings for type = cloud_vc returns Product Offerings which includes properties describing handover_metro_area, handover_metro_area_network, service_metro_area, service_metro_area_network, service_provider_pop, and service_provider_pop_name. What is missing is the service_pop and we would like to add this as an optional array property to product-offerings. The purpose of the property is to explicitly show the location of the NNI that will be used on the service side to connect to the service providers.

For example, at DLR we have on ramps in London for all CSP on our A and B networks, where these on-ramp are specifically in the Pop locations LON1-A and LON1-B. Adding the additional property will provide explicit visibility of the Pop locations that will be utilised for the Cloud Service. The revised response with the property added would like below. The change would not allow the requestor to pick the exact Pop, just the availability-zone as per previous enhancement.

{
		"id": "ms-express-route.London.LON",
		"physical_port_speed": 0,
		"bandwidth_max": 2000,
		"bandwidth_min": 0,
		"service_provider_pop": "London",
		"service_provider_pop_name": "London",
		"service_provider_region": "Europe North",
		"resource_type": "network_service",
		"provider_vlans": "multi",
		"delivery_method": "shared",
		"service_provider_workflow": "provider_first",
		"display_name": "Microsoft ExpressRoute",
		"downgrade_allowed": false,
		"handover_metro_area": "LON",
		"handover_metro_area_network": "LON",
		"name": "Microsoft ExpressRoute",
		"service_provider": "Microsoft",
		"type": "cloud_vc",
		"upgrade_allowed": true,
		"service_metro_area": "LON",
		"service_metro_area_network": "LON",
                "service_pop":["LON1-A","LON2-B"],
		"diversity": 2
	},
```~~~~