Support for new HttpChecksum trait for requests and responses

[joviegas]

Motivation and Context

This PR will support adding of Http Checksum for request and automatically validating Http Checksum for responses based on the httpChecksum trait defined in the model

    "PutOperationWithChecksum":{
      "name":"PutOperationWithChecksum",
      "http":{
        "method":"PUT",
        "requestUri":"/"
      },
      "input":{"shape":"PutOperationRequest"},
      "output":{"shape":"PutOperationResponse"},
      "httpChecksum" : {
        "requestChecksumRequired": true,
        "requestAlgorithmMember": "ChecksumAlgorithm"
      }
    },
    "GetOperationWithChecksum":{
      "name":"GetOperationWithChecksum",
      "http":{
        "method":"GET",
        "requestUri":"/"
      },
      "input":{"shape":"GetOperationRequest"},
      "output":{"shape":"GetOperationResponse"},
      "httpChecksum" : {
        "requestValidationModeMember": "ChecksumMode",
        "responseAlgorithms": ["CRC32C", "CRC32", "SHA1", "SHA256"]
      }
    },

• Example
  • For PutOperationWithChecksum as above , http Checksum will be calculated as per the checksum defined in ChecksumAlgorithm field of its input request that is PutOperationRequest in this case.
  • For GetOperationWithChecksum as above, validation is supported for following algorithms ["CRC32C", "CRC32", "SHA1", "SHA256"] and the response is validated based on the ChecksumMode field of the outputResponse that is GetOperationResponse.

Modifications

• Codegen changes to identify and add required attributes when an operation is maked with httpChecksum traits.
• Interceptors to add the checksums
• Signer modification to add Checksum while reading the payload for signing.

Testing

• Local builds.
• Integ test as part of this PR checks

Screenshots (if appropriate)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

Checklist

• I have read the CONTRIBUTING document
• Local run of mvn install succeeds
• My code follows the code style of this project
• My change requires a change to the Javadoc documentation
• I have updated the Javadoc documentation accordingly
• I have added tests to cover my changes
• All new and existing tests passed
• I have added a changelog entry. Adding a new entry must be accomplished by running the scripts/new-change script and following the instructions. Commit the new file created by the script in .changes/next-release with your changes.
• My change is to implement 1.11 parity feature and I have updated LaunchChangelog

License

• I confirm that this pull request can be released under the Apache 2 license

[Bennett-Lynch]

Should this still be in software.amazon.awssdk.core.internal?

Same feedback for any other classes that were escalated from @SdkInternalApi to @SdkProtectedApi.

[joviegas]

Good catch, this class is extended and used only by internal classes, this should be reverted back to @SdkInternalApi
as it was before #2780

[sonarqubecloud]

SonarCloud Quality Gate failed.   

7 Bugs
0 Vulnerabilities
1 Security Hotspot
12 Code Smells

77.4% Coverage
1.3% Duplication