Add Internal Error Types and Map to Public Types in Storage

[alzimmermsft]

Description

Adds new internal exception types to the Storage SDKs to handle an issue found running performance tests where if there is an error response from the service conveyed in the HTTP response body it was running into a linkage error attempting to initialize Jackson's XmlMapper (which it can no longer do with the dependency removed).

The root cause of this issue is that the exception types that were being used in the generated code for Storage had Object as the exception value, which leads azure-core attempting to deserialize into Object which doesn't have support. This also meant if a customer were to interact with the exception type the value would have no immediate meaning as Object is very generic.

This PR prototypes a fix to this issue by using internal types to be the exception used in generated code where they have a value that is typed and contains fields based on what the Storage service returns.

Another possible solution to this issue is breaking the API of the existing Storage exceptions to use a specific typed value. Won't be done as this is a breaking change. This could be a future change if / when there are other breaking changes planned.

All SDK Contribution checklist:

• The pull request does not introduce [breaking changes]
• CHANGELOG is updated for new features, bug fixes or other significant changes.
• I have read the contribution guidelines.

General Guidelines and Best Practices

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes.

[azure-sdk]

API change check

API changes are not detected in this pull request.

[alzimmermsft]

/azp run java - storage - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).