[Storage] Show more error information when cmdlet failed with StorageException

[blueww]

Description

Will add the information in StorageException.RequestInformation.ExtendedErrorInformation, which include: ErrorCode, ErrorMessage, ExtendedErrorInformation, if they exist

Such as for Set-AzStorageShareQuota, when input invalid quota, the original error is:

PS C:\temp>   Set-AzStorageShareQuota -ShareName $containerName -Quota 50000 -Context $ctx
Set-AzStorageShareQuota : The value for one of the HTTP headers is not in the correct format. HTTP Status Code: 400 - HTTP Error Message: The value for one of the HTTP headers is not 
in the correct format.
At line:1 char:1
+   Set-AzStorageShareQuota -ShareName $containerName -Quota 50000 -Con ...
+   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : CloseError: (:) [Set-AzStorageShareQuota], StorageException
    + FullyQualifiedErrorId : StorageException,Microsoft.WindowsAzure.Commands.Storage.File.Cmdlet.SetAzureStorageShareQuota

After change, the error is:

PS C:\temp>   Set-AzStorageShareQuota -ShareName $containerName -Quota 50000 -Context $ctx
Set-AzStorageShareQuota : The value for one of the HTTP headers is not in the correct format. HTTP Status Code: 400 - HTTP Error Message: The value for one of the HTTP headers is not 
in the correct format.
ErrorCode: InvalidHeaderValue
ErrorMessage: The value for one of the HTTP headers is not in the correct format.
RequestId:7a1f736b-101a-001a-5edd-24f3e4000000
Time:2019-06-17T07:23:11.8786920Z
HeaderName: x-ms-share-quota
HeaderValue: 50000
At line:1 char:3
+   Set-AzStorageShareQuota -ShareName $containerName -Quota 50000 -Con ...
+   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : CloseError: (:) [Set-AzStorageShareQuota], StorageException
    + FullyQualifiedErrorId : StorageException,Microsoft.WindowsAzure.Commands.Storage.File.Cmdlet.SetAzureStorageShareQuota

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]

@cormacpayne
Thanks for the quick review and merge!