fix(clients): populate message field when parsing errors

[trivikr]

Issue

Refs: smithy-lang/smithy-typescript#597

Description

Populates message field when parsing errors. This is required, as service response may populate error message in Message even though it's modeled to be in message.

Testing

• CI is successful.
• Integration tests are successful.
• Detailed testing will be done by ensuring elasticache error test does not fail after AWSQueryError trait is reintroduced (repeat of feat: Support awsQueryError trait #3174 which was reverted in chore: revert support for awsQueryError trait #3193):

  1) Scenario: Error handling # features/elasticache/elasticache.feature:15
    ✔ Before # features/elasticache/step_definitions/elasticache.js:3
    ✔ Before # features/extra/hooks.js:15
    ✔ Given I create a cache parameter group with name prefix "" # features/elasticache/step_definitions/elasticache.js:9
    ✔ Then the error code should be "InvalidParameterValue" # features/extra/hooks.js:93
    ✖ Then the error message should contain: # features/extra/hooks.js:99
        """
        The parameter CacheParameterGroupName must be provided and must not be blank
        """
        AssertionError [ERR_ASSERTION]: Expected InvalidParameterValue to match The parameter CacheParameterGroupName must be provided and must not be blank
            at Function.assertMatches [as match] (/codebuild/output/src969879309/src/root/release-artifacts/aws-sdk-js-v3/features/extra/assertions.js:4:10)
            at Object.<anonymous> (/codebuild/output/src969879309/src/root/release-artifacts/aws-sdk-js-v3/features/extra/hooks.js:103:23)
  

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.