Upgrading the rest of the components using AWS to V2

[mikeee]

Describe the feature

Components outstanding are (with work size estimate):

• (Common) Kafka aws path - L

Deprioritised:

• Bindings.s3 - L - fix: upgrade straggler v1 import #3910
• Bindings.ses - M - fix: upgrade ses binding to use awsv2 #3911
• Bindings.kinesis - M - Feat/kinesis binding vmware go kcl v2 latest #4082
• Bindings.sns - M
• Bindings.sqs - M
• Configuration.postgres (migrate to new common provider) - S
• Conversation.bedrock (migrate to new common provider) - S - feat: upgrade bedrock to v2 #3909
• SecretStore.parameterstore - S - feat: upgrade paramstore to v2 #3908
• SecretStore.secretmanager - S - feat: upgrade aws secrets manager to v2 #3901

Stretch goals would be to migrate tests to v2 although as a lower priority, the tests work regardless of v1/v2 and the focus should be on stability as opposed to overhauling the tests as of yet

Release Note

RELEASE NOTE: UPDATE All components interface with AWS using the V2 sdk

[peterdalinis-scout]

Is github.com/vmware/vmware-go-kcl-v2 also part of this upgrade?

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.