Add AWS SDK's sts dependency to relevant modules to fix IRSA

[sidharrth2002]

What

Add software.amazon.awssdk:sts dependency to potentially resolve error caused by AWS v2 SDK.

The relevant error here was raised by @larrywax, relating to using IRSA credentials. Namely, this line was in the error log:

WebIdentityTokenCredentialsProvider(): To use web identity tokens, the 'sts' service module must be on the class path.,

How

Airbyte's use of the AWS v2 SDK for S3 data retrieval might require adding software.amazon.awssdk:sts due to a hardcoded class path in AWS's WebIdentityTokenCredentialsProvider causing errors.

Recommended reading order

1. deps.toml
2. airbyte-commons-worker/build.gradle
3. airbyte-config/config-models/build.gradle
4. airbyte-server/build.gradle
5. airbyte-workers/build.gradle

Can this PR be safely reverted / rolled back?

If you know that your PR is backwards-compatible and can be simply reverted or rolled back, check the YES box.

Otherwise if your PR has a breaking change, like a database migration for example, check the NO box.

If unsure, leave it blank.

• YES 💚
• NO ❌

🚨 User Impact 🚨

Are there any breaking changes? What is the end result perceived by the user? If yes, please merge this PR with the 🚨🚨 emoji so changelog authors can further highlight this if needed.

[weichunnn]

Thanks for bringing up the changes to resolve the missing STS module!

[weichunnn]

Found other modules which are relying on implementation libs.s3 here. I think we can include the STS module there as well to have better coverage. What do you think?

[sidharrth2002]

Agreed @weichunnn, I've added this as well to airbyte-commons-server and airbyte-container-orchestrator

[pmossman]

Thanks for the continued contributions in this area @weichunnn and @sidharrth2002! I'll open this PR in our internal repo and run tests there.

[pmossman]

/create-oss-pr

[pmossman]

@sidharrth2002 @weichunnn sorry for the delay here - the internal build was failing and I didn't have time to investigate until today. Turns out there was a small issue with our PR-cloning tool and the fix was simple, so I went ahead and merged the internal PR. The changes will be reflected back to this public repo, and the fix will be available in the next OSS release. Thanks again!