Review and Upgrade Deprecated Packages

[javiertoledo]

Several packages across various Booster packages have been deprecated and require review and potential upgrades to ensure continued functionality, security, and maintainability.

Pending deprecated dependencies per package

application-tester

• [email protected] - Moved to Drop the deprecated dependency graphql-transport-ws in favor of graphql-ws #1476, as it requires major and potentially breaking changes

framework-types

• `@types/[email protected] - Addressed in Upgrade deprecated packages CLI and framework-types #1485

framework-provider-aws-infrastructure (Currently Deprecated)

• @types/[email protected]

framework-provider-aws (Currently Deprecated)

• [email protected] - Used by aws-sdk v2
• [email protected] - Used by aws-sdk v2

cli

• [email protected], @types/[email protected], and @oclif/[email protected] - Addressed in Upgrade deprecated packages CLI and framework-types #1485

framework-provider-azure-infrastructure

• @npmcli/[email protected] - Needs to update cdktf at least to v18.1

framework-integration-tests

• [email protected] - Used by serverless/platform-client even in the latest version
• [email protected] - Used by serverless/json-refs even in the latest version

Plan

For each dependency:

• Upgrade each package to the latest stable version that resolves the deprecation warning, while ensuring compatibility with our existing codebase or applying the needed changes.
• Test the upgrades thoroughly to ensure no regressions are introduced, and that all functionalities continue to work as expected.
• Update any related documentation to reflect changes in package versions and any necessary code adjustments.

The goal is to keep our codebase up to date, secure, and maintainable by addressing these deprecations proactively. Take into account that:

• This issue is targetted for the upcoming v2.0.0 release, so introducing breaking changes is acceptable.
• Make sure that any API changes are properly documented in the documentation.
• Feel free to work on each package in a different branch and PR. Make sure to target your PRs to the v2.x.x branch.