Allow integrity checks during upload

[gnarula]

Adds a configuration that enables integrity checks using Content-MD5 headers for each chunk of a multi-part upload.

This would be useful to users who want to ensure no data corruption occurs during the upload.

Unfortunately, S3Mock doesn't check the header and therefore I couldn't write a test for it but the feature is documented here and the encoding is documented here and here

I'll be glad to add a test if there's an alternative to it

[ghost]

@confluentinc It looks like @gnarula just signed our Contributor License Agreement. :+1:

Always at your service,

clabot

[gnarula]

@kkonstantine Can you have a look at this please and suggest some feedback?

P.S. I wasn't sure whom to request for a review and I just went by the contribution count...

[kkonstantine]

Thanks for the PR @gnarula . Adding more people for review. I'll try to find some time to take a look too. The lack of support in unit tests is unfortunate.

[raphaelauv]

any news ?

[cjolivier01]

This PR has conflicts that would need to be resolved before review.

[kpatelatwork]

@C0urante @cjolivier01 also there are no unit/integration tests so we should add them. We should put this ticket in pipeline

[wpoch]

This PR is needed if we want to enable S3 Object Lock, otherwise it failed with:

Caused by: com.amazonaws.services.s3.model.AmazonS3Exception: Content-MD5 OR x-amz-checksum- HTTP header is required for Put Part requests with Object Lock parameters (Service: Amazon S3; Status Code: 400; Error Code: InvalidRequest; Request ID: SZFBSMA800XKHS0Y; S3 Extended Request ID: TjXtXuZl0UMCbHbwBb4FSrdTqHWgE37isKsngfW4rbgda3dvJXj9aOFvuiTobLEe9UOS+G/SFzk=; Proxy: null), S3 Extended Request ID: TjXtXuZl0UMCbHbwBb4FSrdTqHWgE37isKsngfW4rbgda3dvJXj9aOFvuiTobLEe9UOS+G/SFzk=

[wwakas]

Any updates here? Like the above comment, this change is needed when the s3 object-lock feature is enabled on the bucket.