feat(stepfunctions-tasks): add Node.js 22 support to EvaluateExpression

[claypack]

Issue # (if applicable)

Closes #35353.

Reason for this change

Currently you are unable to specify the NodeJS 22 Runtime directly in the EvaluateExpression construct. When users try to use Runtime.NODEJS_22_X, they receive an error that this runtime is not supported.

Description of changes

• Added Node.js 22 runtime mapping to the nodeJsGuids object in evaluate-expression.ts with UUID 'b64e1fb8-9c89-4f7d-8a34-2e2a1c5f6d7e'
• Added unit test coverage for Node.js 22 runtime in evaluate-expression.test.ts

The changes follow the exact same pattern as existing Node.js runtime support (Node.js 20, 18, etc.). No alternatives were considered as this is a straightforward addition to the existing runtime mapping system. The UUID was generated to ensure uniqueness for the singleton Lambda function pattern used by EvaluateExpression.

Describe any new or updated permissions being added

No new or updated IAM permissions are required. This change only adds support for an additional Lambda runtime version.

Description of how you validated changes

• Added unit test that verifies EvaluateExpression creates a Lambda function with nodejs22.x runtime
• All existing tests continue to pass (5/5 tests passing)
• Manually tested by creating a CDK app, synthesizing CloudFormation template, and deploying to AWS
• Verified the deployed Lambda function uses Node.js 22 runtime and executes successfully and returns

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[aws-cdk-automation]

(This review is outdated)

[alvazjor]

Hi @claypack
Thanks for the contribution. We have some integ tests for the EvaluateExpression resource: packages/@aws-cdk-testing/framework-integ/test/aws-stepfunctions-tasks/test/integ.evaluate-expression-default-runtime.ts
Can you create a similar one using the new NodeVersion you are adding, please? Thanks

✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.