Lack of support for x-ms-skip-url-encoding causes incorrect request URLs

[thomas11]

Way back in #20 we determined that we didn't need the x-ms-skip-url-encoding of the Azure spec at the time. That has changed in the meantime.

For instance, azure-native:authorization:RoleDefinition has this path in metadata: /{scope}/providers/Microsoft.Authorization/roleDefinitions/{roleDefinitionId}. A typical scope like in our examples/keyvault test is /subscriptions/123.... Note that it contains two slashes.

Since it’s a URL path parameter, the provider escapes scope to %2Fsubscriptions%2F0123.... That is incorrect since the scope property is annotated with x-ms-skip-url-encoding, and leads to an incorrect request URL.

Fortunately, everything works in this case, probably because the Azure endpoint is forgiving of its input. We should still fix this, though.