[Storage] Upgrade to XSCL 10 (depends on PR #9037, to upgrade SRP SDK)

[blueww]

Description

This PR is mainly to upgrade to Azure Storage Client library(aka: XSCL) 10.0.1.
It also include the code change of PR #9037
（Since we need to upgrade both SDK in Build release, and they have some code change need merge）

For XSCL 10.0.1:

The namespace of XSCL changed from Microsoft.WindowsAzure.Storage.* to Microsoft.Azure.Storage.*, so:

1. Added many breaking change exception, since the output/input type namespace change . (Confirmed with Mark, this is not real breaking, as long as the content of the type not change)
2. Move some file original in shared XSCL swapper to storage folder, since the namespace change of XSCL
3. Modify some test cases to add support to -asjob, and queue namespace change.

For SRP SDK 11.0:

The storage account Kind in SRP SDK is change from a enum to string, but the value is same.
So the PSStorageAccount.Kind also change type to string, but the value is same, so it won't block customer script.

There're 2 breaking changes :

1. change output type of New/Get/Set-AzStorageAccount : The PSStorageAccount.Sku.Name value is changed ('-' added). The Change is expected, since in New/Set-AzStorageAccount cmdlet, the input SkuName has '-' (before, the output don't have '-'), so with the change the input and output Sku Name value will be aligned.
   "StandardLRS" -> "Standard_LRS";
   "StandardGRS" -> "Standard_GRS";
   "StandardRAGRS" -> "Standard_RAGRS";
   "StandardZRS" -> "Standard_ZRS";
   "PremiumLRS" -> "Premium_LRS";
   "PremiumZRS" -> "Premium_ZRS";

2. The default Storage Account Kind in New-AzStorageAccount is changed to StorageV2. Since per SRP team, this should be the default Storage Kind.

Checklist

• I have read the Submitting Changes section of CONTRIBUTING.md
• The title of the PR is clear and informative
• The appropriate change log has been updated
• [] The PR does not introduce breaking changes
• If applicable, the changes made in the PR have proper test coverage
• For public API changes to cmdlets:
  • the changes have gone through a cmdlet design review (Microsoft internal partners only)
  • the cmdlet markdown files were generated using the platyPS module

[blueww]

Currently we use private (not signed) DMlib. Will upgrade to signed one when DMlib release.
There are some test cases failed since DMlib not signed.

Would you please first help to review the PR,but don't merge until I upgrade to signed DMlib?

[blueww]

@markcowl

Would you please help to review this? We target this PR for Build release.
This only build failure is caused by the test machine issue:
Error message is:

The command "sudo apt-get install -qq dotnet-sdk-2.1=2.1.400*" failed and exited with 100 during

[markcowl]

Waiing on #9037

[blueww]

@markcowl

I have fixed the merge conflict, but the build failed on powershell-core still fail for same issue, would you please help to look?

/.azure-pipelines/powershell-core.yml: Could not find /.azure-pipelines/util/analyze-steps.yml in repository self hosted on https://api.github.com using commit 3f9776c. GitHub reported the error, "Not Found"

[blueww]

@markcowl
I have resolved the merge conflict. Please help to review.

[blueww]

@markcowl
The build check pass for this PR, and the conflict is resolved.
Would you please help to review and merge this PR if no other issue?
Thanks!