HDDS-16674. Bump awssdk to 2.55.4

[dependabot]

Bumps software.amazon.awssdk:bom from 2.54.18 to 2.55.4.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[adoroszlai]

@ivandika3 ListDirectoryBucketsTests started failing with version 2.54.20. Release notes only mentions "Performance Improvements" for S3 services in that version. Can you please check?

NullPointerException: Bucket must not be null
	at software.amazon.awssdk.utils.Validate.notNull(Validate.java:119)
	at software.amazon.awssdk.services.s3.internal.s3express.S3ExpressIdentityKey.<init>(S3ExpressIdentityKey.java:40)
	at software.amazon.awssdk.services.s3.internal.s3express.S3ExpressIdentityKey$Builder.build(S3ExpressIdentityKey.java:119)
	at software.amazon.awssdk.services.s3.internal.s3express.DefaultS3ExpressIdentityProvider.lambda$resolveIdentity$0(DefaultS3ExpressIdentityProvider.java:54)
	...
	at software.amazon.awssdk.core.http.auth.AuthSchemeResolver.resolveIdentity(AuthSchemeResolver.java:294)
	at software.amazon.awssdk.core.http.auth.AuthSchemeResolver.trySelectAuthScheme(AuthSchemeResolver.java:281)
	at software.amazon.awssdk.core.http.auth.AuthSchemeResolver.selectAuthScheme(AuthSchemeResolver.java:109)
	...
	at software.amazon.awssdk.services.s3.DefaultS3Client.listDirectoryBuckets(DefaultS3Client.java:9324)
	at org.apache.hadoop.ozone.s3.awssdk.v2.AbstractS3SDKV2Tests$ListDirectoryBucketsTests.testListDirectoryBucketsPaginationReturnsAllBuckets(AbstractS3SDKV2Tests.java:4409)

[ivandika3]

@adoroszlai Thanks for highlighting the issue.

From a short research this is related to the S3 Express session auth, but can also be a bug in the AWS SDK V2 itself. Although Ozone supports "directory" buckets (i.e. FSO buckets), Ozone does not support the S3 session token as mentioned in HDDS-9815.

From Ozone side, one possible solution is to set disableS3ExpressSessionAuth(true) to avoid the S3 session credentials issue. However, the issue can also be a AWS SDK V2 issue, let me dig deeper and get back to you.

[dependabot]

Superseded by #11407.