Chk 3709 upgrade to node 22 tests

[EmanueleBVtech]

List of Changes

Updated from node 18 to 22.
Added clusterization setup to improve CPU usage.

Motivation and Context

Support for Node.js 18 ends on 30 April 2025—upgrade your apps to Node.js 20 
You’re receiving this email because you have one or more Node.js 18 app(s) on Azure Functions.

On 30 April 2025, support for Node.js 18 will end. Your apps that are hosted on Azure Functions will continue to run, but security updates will no longer be available, and we’ll no longer provide customer service for Node.js 18. If you're running functions apps using an unsupported runtime or language version, you may encounter issues and performance implications and will be required to upgrade before receiving support for your function app. Learn more about Azure Functions stack version support.

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Please upload report for BASE (main@c549076). Learn more about missing BASE report.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #93   +/-   ##
=======================================
  Coverage        ?   87.58%           
=======================================
  Files           ?       10           
  Lines           ?      306           
  Branches        ?       39           
=======================================
  Hits            ?      268           
  Misses          ?       31           
  Partials        ?        7           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[github-actions]

This PR exceeds the recommended size of 400 lines. Please make sure you are NOT addressing multiple issues with one PR. Note this PR might be rejected due to its size.