fix: throw S3EC error on GCM key/IV reuse

[rishav-karanjit]

Issue #, if available:
#510

Description of changes:

This is a little bending change as expected error type is getting change but I don't think consumers of S3EC will be depending on the JCE error.

When crossRegionAccessEnabled(true) triggers a redirect, the SDK re-subscribes to the request body, which would reuse the same AES-GCM key/IV. This change wraps the encrypted request body in NoRetriesAsyncRequestBody to proactively block re-subscription with a clear S3EncryptionClientException instead of low-level error message thrown by JCE provider.

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

Check any applicable:

• Were any files moved? Moving files changes their URL, which breaks all hyperlinks to the files.