Upgrade AWS SDK to v3

[javiertoledo]

As we consider upgrading to Node.js runtime v18 in our AWS Lambda environment, there are a couple of notable implications regarding AWS SDK management:

1. AWS SDK v2 Deployment with Node.js v18:

   • If we opt to retain AWS SDK v2, we'd need to deploy it manually with each Lambda function, as per the AWS announcement.

2. Upgrading to AWS SDK v3:

   • Alternatively, upgrading to AWS SDK v3 could streamline the deployment process since it comes preloaded with the Node.js v18 runtime. This approach could also potentially simplify the management of AWS SDK within our projects.

3. Deprecated Types Package Removal:

   • Additionally, the deprecated package ...framework-provider-aws-infrastructure | WARN deprecated @types/[email protected] can likely be removed from our dependencies. According to the npm registry, AWS SDK now provides its own type definitions, rendering this package obsolete.

Originally suggested by @samueldominguez in #1431 (comment)

[javiertoledo]

While the AWS provider has been discontinued (See #1477) due to issues with the AWS CDK, the deployment scripts are still functional, and the library part of the provider is not affected, as it is using the AWS SDK. It would be worth upgrading the AWS integration as this part could be reused if the infrastructure package is rewritten using the CDK v2 or an alternate deployment strategy.