Upgrade GitHub Actions for Node 24 compatibility

[salmanmkc]

Summary

Upgrade GitHub Actions to their latest versions to ensure compatibility with Node 24, as Node 20 will reach end-of-life in April 2026.

Changes

Action	Old Version(s)	New Version	Release	Files
actions/checkout	v2, v4	v6	Release	assigner.yml, blossom-ci.yml, build-tensorrt-linux.yml, build-tensorrt-windows.yml, build-test-linux-aarch64-jetpack.yml, build-test-linux-aarch64.yml, build-test-linux-x86_64.yml, build-test-linux-x86_64_rtx.yml, build-test-tensorrt-linux.yml, build-test-tensorrt-windows.yml, build-test-windows.yml, build-test-windows_rtx.yml, build_linux.yml, build_windows.yml, docgen.yml, docker_builder.yml, linter.yml, linux-test.yml, nightlies.yml, release-linux-aarch64.yml, release-linux-x86_64.yml, release-windows.yml, windows-test.yml
actions/download-artifact	v4	v7	Release	linux-test.yml, windows-test.yml
actions/labeler	v4	v6	Release	label.yml
actions/setup-java	v1	v5	Release	blossom-ci.yml
actions/setup-python	v5	v6	Release	build-test-linux-aarch64-jetpack.yml, build-test-linux-aarch64.yml, build-test-linux-x86_64.yml, build-test-linux-x86_64_rtx.yml, build-test-tensorrt-linux.yml, build-test-tensorrt-windows.yml, build-test-windows.yml, build-test-windows_rtx.yml, build_windows.yml, linter.yml, release-linux-aarch64.yml, release-linux-x86_64.yml, release-windows.yml
actions/stale	v1	v10	Release	stale.yml
actions/upload-artifact	v4	v6	Release	build-tensorrt-linux.yml, build-tensorrt-windows.yml, build_linux.yml, build_windows.yml, linux-test.yml

Context

Per GitHub's announcement, Node 20 is being deprecated and runners will begin using Node 24 by default starting March 4th, 2026.

Why this matters

• Node 20 EOL: April 2026
• Node 24 default: March 4th, 2026
• Action: Update to latest action versions that support Node 24

Security Note

Actions that were previously pinned to commit SHAs remain pinned to SHAs (updated to the latest release SHA) to maintain the security benefits of immutable references.

Testing

These changes only affect CI/CD workflow configurations and should not impact application functionality. The workflows should be tested by running them on a branch before merging.