Fix flaky test DynamoDbJavaClientRetryOnTimeoutIntegrationTest

[S-Saranya1]

Motivation and Context

The test uses a 2ms apiCallAttemptTimeout which is so short that the connection gets cancelled before the SDK can wrap the timeout as ApiCallAttemptTimeoutException, resulting in CancellationException or ConnectionShutdownException instead.

Modifications

Increased apiCallAttemptTimeout from 2ms to 5ms. Still reliably too short for a DynamoDB listTables round trip (~50-200ms), but long enough for the SDK's timeout wrapper to fire properly.

Testing

Ran the test locally with timeout values of 2, 5, 10, 15, and 20ms(10 runs each).
Results:

• 2ms: 8/10 correct, 2/10 CancellationException
• 5ms: 10/10 correct
• 10ms: 10/10 correct
• 15ms: 10/10 correct
• 20ms: 10/10 correct

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