Enable setting multipart to true/false by defining it as a custom client context parameter

[anirudh9391]

Multipart upload can be set as a client configuration parameter and is accessible at the time of instantiation. This allows classes that instantiate the S3AsyncClient to validate this parameter.

Modifications

1)Incorporated multiPartEnabled as a custom client configuration parameter by defining it in customization.config. The codegen module generates getter and setter methods for this parameter.
2) By default, set multipartEnabled = true in the S3AsyncClient
3) Removed code that sets multiPart Enabled on the client directly

Testing

Unit Tests to validate that

1. Disabling multiPart code path logs warnings
2. Default S3AsyncClient has multiPartEnabled = true by default.
3. Setting MultiPartEnabled = true does not log warnings

Screenshots (if appropriate)

Types of changes

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

Checklist

• [ x] I have read the CONTRIBUTING document
• [ x] Local run of mvn install succeeds
• [ x] 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
• [x ] I have added tests to cover my changes
• [ x] 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

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

[L-Applin]

This also adds the multipart-enable config and method to the sync version of the client, as it adds the method the S3BaseClientBuilder interface which is used by both the sync and async builders:

S3Client client = S3Client.builder()
    .multipartEnabled(true) // <--- should not be available on sync builder
    .build();

I think we should avoid being able to define this config on the sync client and keep it on the async client only

[L-Applin]

very nit-picky: I'd avoid \n in logs

[L-Applin]

There seems to still be a checkstyle violation:

2024-02-12T18:43:35.7470507Z [ERROR] Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin:3.1.2:check (checkstyle) on project s3-transfer-manager: Failed during checkstyle execution: There is 1 error reported by Checkstyle 8.42 with software/amazon/awssdk/checkstyle.xml ruleset. -> [Help 1]

[sonarcloud]

Quality Gate failed

Failed conditions
C Reliability Rating on New Code (required ≥ A)

See analysis details on SonarCloud

Catch issues before they fail your Quality Gate with our IDE extension SonarLint