fix(AWSLocation): Fixing clock skew retries

[sebaland]

Description of changes:

This PR fixes the retry mechanism when dealing with clock skews in AWSLocation. The logic is actually implemented in the AWSURLRequestRetryHandler, but it depends on both the error domain and code to be from AWSService itself.

Because the AWSLocation service defines its own error domain and codes, the conditions were never met and isClockSkewError always evaluated to false.

So I've just added some code to handle cases in which the error can be mapped to a "vanilla" AWSService error instead, which then makes the retry mechanism work.

Note: This is actually affecting every AWS service that defines its own set of errors and does not override the proper methods in AWSURLRequestRetryHandler. It should be fixed

Check points:

• Added new tests to cover change, if needed
• All unit tests pass
• All integration tests pass
• Updated CHANGELOG.md
• Documentation update for the change if required
• PR title conforms to conventional commit style

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.