Upgrade AWS SDK

[binh-dam-ibigroup]

Checklist

• Appropriate branch selected (all PRs must first be merged to dev before they can be merged to master)
• Any modified or new methods or classes have helpful JavaDoc and code is thoroughly commented
• The description lists all applicable issues this PR seeks to resolve
• [na] The description lists any configuration setting(s) that differ from the default settings
• All tests and CI builds passing

Description

This PR upgrades AWS SDK to version 2.x. The largest benefit of upgrading is AWS access using federated (SSO) login during development without having to use temporary access keys. Existing access-key-based access should still work. Also, AWS SDK 1.x is out of support now.

Things to test:

• Import a feed version and download that feed version (using a config where application.data.use_s3_storage = true).
• Deploy an OTP instance (using a config where modules.deployment.enabled = true

[binh-dam-ibigroup]

@miles-grant-ibigroup and @daniel-heppner-ibigroup in case you are interested by the changes in upgrading AWS SDK.

[binh-dam-ibigroup]

A few minor comments. AWS related tests pass, I'm assuming actual AWS end to end testing using DT have been carried out on a test environment.

@br648 I had not when first submitting the PR, but now we have a successful E2E test run with this PR's code:
ibi-group/datatools-ui#1068

[miles-grant-ibigroup]

Should we update build-docker.yml to build a docker image for this branch? Then we can test on a real server

[binh-dam-ibigroup]

Should we update build-docker.yml to build a docker image for this branch? Then we can test on a real server

Good idea (81aeb19)

[miles-grant-ibigroup]

Everything is working on a real server. Thanks so much for figuring this out!

[binh-dam-ibigroup]

@br648 and @miles-grant-ibigroup Requesting approvals again after stale code rule.