Provider - Reinstate Service Name for AGO Compatibility

With Azure's automated deployment, I could test integration for production Feature Service and ArcGIS Online. I found that our removal of the optional Feature Service name has resulted in broken compatibility with ArcGIS Online Mapping Clients, as AGO expects a Feature Service name when you add a layer as a Portal item.

Proposed Solution

• Reinstate the gcz Feature Service name to restore compatibility.
• Consider enforcing gcz as the Feature Service name, or possibly making it configurable.