fix: Handle default authentication for SQS

[lemaitre-aneo]

Motivation

Current SQS implementation requires credentials to be passed in environment variables, and does not support aws config file or pod service account on kubernetes.

Description

Use the package AWSSDK.SecurityToken to handle the default authentication for AWS services, as it's currently done for S3 Adapter.

Testing

Test has been done locally with localstack, as well as on AWS with an actual SQS, and bindings between Kubernetes service account and IAM role.

Impact

When both S3 and SQS is configured to use the IAM roles through Kubernetes service account, there is a loading issue for the AWSSDK.SecurityToken assembly while creating a SQS client.

Checklist

• My code adheres to the coding and style guidelines of the project.
• I have performed a self-review of my code.
• I have commented my code, particularly in hard-to-understand areas.
• I have made corresponding changes to the documentation.
• I have thoroughly tested my modifications and added tests when necessary.
• Tests pass locally and in the CI.
• I have assessed the performance impact of my modifications.