Upgrade to Node 24

[slifty]

There isn't any reason to use anything but active node, as far as I can tell.

[github-actions]

QA Instructions

Summary

This PR updates the Node.js version used in the project from 20 to 24. Relevant files, including .node-version, action.yml, package.json, and tsconfig.json, have been updated to reflect the new Node.js version. Additionally, documentation updates were made to ensure accurate information about the Node.js version policy and upgrade process.

---

Test Environment Setup

1. Ensure Node.js version 24 is installed on your machine. Update your system or use a version manager (e.g., nvm).
2. Run nvm use within the project folder to switch to the specified Node.js version (24).

---

Test Scenarios

1. Verify Environment Setup

1. Ensure the system is running Node.js 24 by executing node -v.
   • Expected Result: v24.x.x is output.
2. Run npm install in the root directory.
   • Expected Result: All dependencies are installed successfully, with no errors.
   • No warnings or errors should occur during installation related to @types/node or the @tsconfig/node24 package.

---

2. Run Application Locally

1. Start the application locally or ensure it's running if applicable to the project.
   • Expected Result: The application starts without issues.

---

3. Validate TypeScript Configuration

1. Run tsc to perform a full TypeScript compilation check.
   • Expected Result: Compilation runs without errors.

---

4. Run Tests

1. Execute the test suite using npm test.
   • Expected Result: All tests pass without errors or failures.

---

5. Verify GitHub Action Compatibility

1. Update the corresponding GitHub Action file(s) in your development/testing branch to point to the updated Node.js runtime (node24).
2. Trigger the CI workflow (e.g., by pushing a test commit).
   • Expected Result: GitHub Actions run successfully using Node.js 24, and workflows complete without errors.

---

6. Confirm Documentation Accuracy

1. Review the README.md file.
   • Expected Result: It correctly mentions "Node 24" and accurately describes the process for updating the Node.js version.
2. Review the AGENTS.md file.
   • Expected Result: The updated Node.js version is mentioned as "Node 24".

---

Regression Risks

1. Breakage in any functionality due to incompatibility with Node.js 24.
   • Verify the functionality of all major workflows (e.g., CI pipelines, GitHub Actions, core application features).
2. TypeScript configuration issues due to the change from @tsconfig/node20 to @tsconfig/node24.
   • Ensure type safety and compatibility are maintained during testing.

---

Things to Watch For

1. Any deprecated or incompatible Node.js 24-specific APIs that might cause runtime failures.
2. Dependency compatibility issues with Node.js 24 (inspect node_modules/ for updated versions or check related changelogs).
3. Integration with external tools, such as GitHub Actions, to ensure they continue operating with Node.js 24.

---

Confirm that all updates, including any resolved bugs or deprecations, are thoroughly tested before approving the PR.

---

Generated by QA Instructions Action