[BUG] `VirtualMachines_List` nextLink is not url encoded

[XiaofeiCao]

Hi team,

Our customer reported a BUG that nextLink returned by VirtualMachines_List is not url encoded, resulting in 400 when requesting using nextLink.

This behavior exists on latest 2023-07-01 and earlier.

According to API guideline,

Note: The service is responsible for performing any URL-encoding required on the nextLink URL.

this should be a bug for the backend. Please help take a look, thanks!

/cc @weidongxu-microsoft

[XiaofeiCao]

Java SDK's workaround effort in PR: Azure/azure-sdk-for-java#36631

Still need backend service fix this issue before we remove the hacky workaround.

[TravisCragg-MSFT]

This has been fixed, closing the issue.

[XiaofeiCao]

@TravisCragg-MSFT Thanks for the information. I have some issue validating the backend response. (met Status code 502, "{"error":{"code":"ProviderError","message":"Resource provider 'Microsoft.Compute' failed to return collection response for type 'virtualMachines'."}}" when listing VMs. Will get back to you later.