AWS v2 SDK for S3

[qqmyers]

What this PR does / why we need it: The v1 AWS SDK Dataverse uses for S3 is in maintenance mode and will reach it's end of life in Dec. 2025. This PR updates Dataverse to use v2.x of the SDK.

Which issue(s) this PR closes:

• Closes AWS S3 SDK end of support on December 31, 2025 #11073

Special notes for your reviewer:

• From initial testing, it looks like the older localstack used in testing does not support the new API. The PR updates to localstack/localstack:4.2.0 in the docker-compose-dev file.

• Sword uses old versions of apache abdera. I've added exclusions to avoid failures with S3. Updating Sword might be a useful thing to do at some point.

Suggestions on how to test this:

• General S3 testing with direct upload and download on and off, with files below and above the min-part-size set for the store (suggest this get set to just over the 5*1024**2 (~5MB) allows by AWS for testing).
• ZipDownloader builds but I am not sure how to test it. As it uses S3, it should be included in testing.

Does this PR introduce a user interface change? If mockups are available, please link/include them here:

Is there a release notes update needed for this change?: inc.

Additional documentation:

[coveralls]

coverage: 23.121% (+0.1%) from 23.007%
when pulling 5c655e2 on GlobalDataverseCommunityConsortium:AWSv2
into cd48216 on IQSS:develop.

[jeromeroucou]

I have done some quick test on our Rados Ceph storage (S3 compatible) and I can upload file only without direct upload. With direct upload, I have a CORS error on my browser. In addition, on (IQSS) develop branch, I don't have this error with same configuration. I'll look at the JS code another day and try to understand it.

[jeromeroucou]

custom-endpoint-url parameter seems to be ignored in direct-upload: the URL who valid CORS is https://bucket.s3.region.amazonaws.com/10.5072/FK2/YZ4INU/196204baf01-d80915a27bbb?X-Amz-Algorithm=AWS4-HMAC-SHA256[...]. If I find some time, I'll try to understand why