AWS SDK Go V2 Migration

[fredjoonpark]

Issue #, if available:

---

Description of changes:

This change upgrades the underlying AWS Go SDK from V1 to V2.

Some notes and highlights regarding significant changes:

• V2 SDK splits services into separate modules
• The config module in V2 introduces a single entry point (config.LoadDefaultConfig()) which consolidates loading AWS credentials
• service client APIs have been refined for more idiomatic Go usage (ie. relying less on aws.String() wrappers and providing typed fields where possible)
• all SDK operations now require a context.Context (supporting graceful cancellation, timeouts)
• the internal request pipeline has been restructured around Smithy middleware. Errors now follow a more consistent structure influenced by Smithy’s model-driven error definitions, making it easier to identify and handle specific error conditions (like ResourceNotFound or AccessDenied) through typed errors rather than relying on string matching
• V2 SDK now uses a dedicated paginator with an iterative interface (HasMorePages() and NextPage()) to handle multi-page API responses. In our context, NextPage performs the network call for fetching query responses (previously QueryPages)
• Added a docker-compose.yml
• Added a new config parameter for setting max write retries
• Updated exception status code to return 400 to match the SDK

Additional resources:

• https://github.com/aws/aws-sdk-go-v2
• https://aws.github.io/aws-sdk-go-v2/docs/migrating/

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[forestmvey]

Thanks for the change.
I have validated the following:

• Integration tests
• Unit tests
• TLS tests
• Correctness tests
• Deployed the connector and tested ingestion
• Deployed the connector and tested remote_read operations