Upgrade for Node 18 compatibility

[javiertoledo]

In this branch we're working on a big upgrade to remove deprecated dependencies and start using Node 18.

TODO

• Raised the node version to 18.18.0
• Review why the core & cli packages unit tests are failing
• Review why the AWS package unit tests are failing
• Increase the node version for Azure Functions - currently set to node 14

Checks

• Project Builds
• Project passes tests and checks
• Updated documentation accordingly

[ghost]

👇 Click on the image for a new way to code review

Legend

[what-the-diff]

PR Summary

• Updated Node.js version in GitHub actions files
  The version of Node.js used in our GitHub workflow files (.github/actions/build/action.yml, .github/workflows/re_test-integration-prepare.yml, etc.) has been updated to 18.18 to maintain up-to-date technology and improve the efficiency of our developments.

• Shifted from Node.js 'Gallium' to 'Hydrogen' in Node Version Manager
  Our Node Version Manager (.nvmrc) has been changed from lts/gallium to lts/hydrogen. This is an upgrade in our underlying Node.js version, aiming at better stability and performance.

• Added a new 'package.json' file
  A 'package.json' file, which forms the basis for Node.js projects and manages dependencies, has been added to further organize the project.

• Updated Node.js version in 'package.json' of several packages
  The Node.js engine version has been updated to the range >=18.0.0 <19.0.0 in multiple packages (packages/application-tester/package.json, packages/cli/package.json, etc.). This ensures that these packages are compatible with our new Node.js version and work optimally.

• Updated Node.js version in Rush Configuration
  The nodeSupportedVersionRange in our rush configuration (rush.json) has been updated from >=16.14.0 <17.0.0 to >=18.0.0 <19.0.0, making Rush compatible with the updated version of Node.js.

• Updated Node.js version in Documentation
  The required Node.js version has also been updated >=18.0.0 <19.0.0 in our documentation files (website/docs/10_going-deeper/data-migrations.md, etc.) to guide users about the updated requirements.

[github-actions]

Oops, looks like you forgot to add a changeset.

⚠️ Please run rush change and commit the changeset file.

This command will prompt you for a change description and generate a changeset file. You can read more about changesets here.

Remember that you should use the version bump that is appropriate for the change you are making:

Version bump	Meaning
patch	Bug fixes, documentation changes, etc.
minor	New features, non-breaking changes
major	Breaking changes

If you are unsure about which version bump to use, please ask in the comments and we will help you out.

[gonzalogarciajaubert]

Azure infrastructure also defines the runtime version in terraform-function-app.ts file. Current version is Node 14:

      siteConfig: {
        applicationStack: {
          nodeVersion: '~14',
        },
      },

I think we should update it too

[gonzalogarciajaubert]

Also I think the functionsExtensionVersion: '~3' needs to be updated to functionsExtensionVersion: '~4' in the same file

[javiertoledo]

/integration sha= 5e85f6e

[github-actions]

⌛ Integration tests are running...

Check their status here 👈

[github-actions]

✅ Integration tests have finished successfully!

[samueldominguez]

@javiertoledo Just an observation: if we want to upgrade the Nodejs runtime to v18, but keep AWS SDK to v2, we'd have to deploy AWS SDK v2 with each lambda. Alternatively, we can upgrade to AWS SDK v3 which comes preloaded with the v18 runtime.

Also, the deprecated package ...framework-provider-aws-infrastructure |  WARN  deprecated @types/[email protected] can just be removed IMO, since AWS SDK seems to provide its own type definitions already, and that seems why it was deprecated in the first place.

[javiertoledo]

@samueldominguez very good observation. Let's upgrade the SDK to v3 before merging this branch. I've created a new issue to track this: #1459

[javiertoledo]

I've moved all pending tasks to separate issues and retargeted this PR to the new v2.x.x base branch. Both unit and integration tests are passing, so I'll merge it.