use class-based temporaryBucketName for s3 stability test buckets

[joviegas]

Motivation and Context

The S3 CRT stability tests hardcode their bucket names via String.format(...)
instead of using the shared S3BucketUtils.temporaryBucketName(...) helper. As a
result their bucket prefixes don't correspond to the test class name (also there is
a typo: s3crtasyncclinet... for S3CrtAsyncClientStabilityTest).

Modifications

Switched the bucket names in the S3 stability tests from hardcoded strings to
temporaryBucketName(<TestClass>.class), so each bucket prefix is derived from its
test class name (consistent with the other S3 integration tests):

• S3CrtAsyncClientStabilityTest (also fixes the clinet typo)
• S3CrtClientStabilityTest
• S3MultipartJavaBasedStabilityTest
• S3NettyAsyncStabilityTest
• S3AsyncWithCrtAsyncHttpClientStabilityTest

S3MockWithAsyncClientStabilityTest is left unchanged — it uses a mock HTTP client
and never creates a real bucket.

The module already depends on service-test-utils, so no new dependency was needed.

License

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

[github-actions]

This pull request has been closed and the conversation has been locked. Comments on closed PRs are hard for our team to see. If you need more assistance, please open a new issue that references this one.