Make the providers and targets in the Azure treeview consistent with the Azure portal

Naming should be aligned. Also consider what we do/don't filter out from the list. This might require a service change, as we don't appear to get 'friendly names' currently.

No file or test is named. Start by comparing the Azure treeview's provider and target entries with the Azure portal, then trace how the service supplies those lists and which filtering is applied; done means the names and inclusion rules are explicitly aligned with the portal.

Written by the indexing model from the issue text.