Update AWS SDK for Java to v2.x

[max402]

the AWS SDK for Java v1.x will enter maintenance mode on July 31, 2024, and reach end-of-support on December 31, 2025.
It is recommended to migrate to v2

[francis-pouatcha]

ToDo:

• add link to aws migration tutorial
• assess the effort needed to perform this migration.

[max402]

Migration Guide
https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/migration.html

End of support anouncement
https://aws.amazon.com/blogs/developer/announcing-end-of-support-for-aws-sdk-for-java-v1-x-on-december-31-2025/#:~:text=Between%20July%2031%2C%202024%20and,or%20changes%20to%20existing%20services.

[Elwizzy12]

• Get Permission to access Amazon S3
• Create a sample project using AWS java SDK for v2 and also making use of streams , before implementing to Datasafe.

[francis-pouatcha]

Contact Stefan, Armand or Dylane for a ticket for an AWS account.

[francis-pouatcha]

Still working on integration tests.

[francis-pouatcha]

Relates to

• Tests fail on latest Minio #349

[Calebasah]

I've encountered issues while testing versioning with Ceph and AWS SDK v2. Specifically:
https://github.com/adorsys/datasafe/blob/develop/datasafe-business/src/test/java/de/adorsys/datasafe/business/impl/e2e/StorageBasedVersioningIT.java

1.Null Version ID:When writing objects with versioning enabled, the versionId is consistently returned as null.
2. Inconsistent Version Reads: When reading by version, the returned content doesn't match the expected version.

It seems Ceph’s versioning might not be fully compatible with AWS SDK v2. I suggest either looking into potential configuration fixes.