fix(ci-cd): bump github actions to node 24 runtimes

[piyushsinghgaur1]

Description

The workflows in this repo emit a Node.js 20 deprecation warning on every run:

Node.js 20 is deprecated. The following actions target Node.js 20 but are being
forced to run on Node.js 24: actions/checkout@v4, actions/setup-node@v4

GitHub has removed Node 20 from its runners and force-runs Node 20 actions on Node 24. Builds still succeed, but the annotation appears on every run and becomes a hard failure once the compatibility shim is dropped.

This moves every affected first-party action onto a major that declares using: node24, and raises any node-version still below 24.

Action pins

File	Was	Now
.github/workflows/release.yaml	actions/checkout@v3	actions/checkout@v5
.github/workflows/release.yaml	actions/setup-node@v3	actions/setup-node@v5

Node versions

File	Was	Now
.github/workflows/release.yaml	'20.x'	'24.x'

Each target major was verified to declare using: node24 by reading its action.yml at the pinned tag.

Deliberately unchanged

• Multi-version test matrices that already include Node 24 are left as-is — collapsing them would drop Node 22 coverage rather than fix a deprecation.
• SHA-pinned third-party actions (e.g. aquasecurity/trivy-action@<sha>) are untouched; SHA pinning is correct practice and unrelated to the Node runtime.

Fixes #27

Type of change

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

• All changed workflow files validated as parseable YAML
• Each target action major confirmed to declare using: node24 in its action.yml
• Bumps confirmed drop-in for the inputs actually used (no input renames or removals across these majors)
• Local pre-commit hook (test + lint) run as part of committing

Scope of this change: 1 file(s) — 1 file changed, 3 insertions(+), 3 deletions(-). CI configuration only; no application source touched.

The warning can be confirmed gone by running a workflow and checking the run summary's Annotations section.

Checklist:

• Performed a self-review of my own code
• npm test passes on your machine
• New tests added or existing tests modified to cover all changes — n/a, CI configuration only, no code paths changed
• Code conforms with the style guide
• API Documentation in code was updated — n/a
• Any dependent changes have been merged and published in downstream modules