[storage] Change generated code Uri.ToString to Uri.AbsoluteUri

[amnguye]

Resolves #11368

Uri.ToString() unencodes the Uri before sending the request to storage. When using a source Uri that has non ascii characters, we will encode the Uri by putting it in the Uri object but unencode it when setting the header.

Switching to using Uri.AbsoluteUri fixes this problem. This fix applies to AppendBlobClient.AppendBlockFromUri. BlockBlobClient.StageBlockFromUri, PageBlobClient.UploadPagesFromUri, FileClient.StartCopy, FileClient.UploadRangeFromUri

This PR also has updates to DataLakeErrorDetails because of the regenerated code.

• Updated generator to convert Uri.ToString to Uri.AbsoluteUri
• Regenerated adding in Error to DataLakeErrorDetails
• Added tests and recordings for non Ascii source blob/file names

[seanmcc-msft]

Looks good.

Why did we make the Data Lake error change?

[amnguye]

Looks good.

Why did we make the Data Lake error change?

Hm. So I assumed someone from our team made the change to the storage swagger and we just haven't regenerated recently, but looks like the change was made by this PR

Azure/azure-rest-api-specs#8739

Should I make a separate PR to make updates to the regenerated code?

[kasobol-msft]

Looks good.
Why did we make the Data Lake error change?

Hm. So I assumed someone from our team made the change to the storage swagger and we just haven't regenerated recently, but looks like the change was made by this PR

Azure/azure-rest-api-specs#8739

Should I make a separate PR to make updates to the regenerated code?

We shouldn't be touching generated code (otherwise process would become non-deterministic at some point). If we were to change this we'd edit readme with generator transforms. However, this is just internal type rename, so we're good.

On the side note. https://github.com/Azure/azure-rest-api-specs/pull/8739/files it seems that we don't have this in 2019-12-12 rest spec. Would be good to get it there as well.

[tg-msft]

Yes - we should make the same swagger change to 2019-12-12 as @kasobol-msft noted. The new Track 2 generators being developed are a lot pickier about correct swagger syntax instead of silently swallowing issues. It's a good thing overall, but will require small changes like this.