Upgrade Platform to Node.js 24 LTS

[Pyatakov]

Problem description

Guardian currently relies on Node.js 20, which reaches end-of-life on April 30, 2026. To ensure continued security, stability, and to benefit from the performance improvements and new capabilities in Node.js 24 LTS, the entire system must be upgraded.
Since our application is microservice-based, every microservice must be updated to run on Node.js 24.
Existing users will receive the new Node version automatically as part of upgrading to the next release of Guardian, without requiring any special actions on their side.

Requirements

• Update all microservices to run on Node.js 24 LTS.
• Update all Dockerfiles to use the official Node.js 24 base images.
• Update build, runtime, and CI/CD configurations to require Node.js 24.
• Ensure the platform functions exactly as before after the switch.
• Update documentation to specify Node.js 24 as the required version (no separate user-facing migration instructions needed).

Definition of done

• Functionality is implemented as specified above.
• New requirements are documented.

Acceptance criteria

• The entire platform runs on Node.js 24 LTS with no regressions.
• All tests complete successfully.
• No Dockerfile or configuration references Node.js 20.
• New and existing users run the updated platform with Node.js 24 automatically upon upgrading the platform version.