Bump icu component version for package nodejs

[SumitJenaHCL]

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• The toolchain has been rebuilt successfully (or no changes were made to it)
• The toolchain/worker package manifests are up-to-date
• Any updated packages successfully build (or no packages were changed)
• Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• All package sources are available
• cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
• All source files have up-to-date hashes in the *.signatures.json files
• sudo make go-tidy-all and sudo make go-test-coverage pass
• Documentation has been updated to match any changes to the build system
• Ready to merge

---

Summary

What does the PR accomplish, why was it needed?
This PR is to bump the icu component version of 78.2

Change Log

• SPECS/nodejs24/nodejs24.signatures.json
• SPECS/nodejs24/nodejs24.spec

Does this affect the toolchain?

NO

Associated issues

• #xxxx

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-YYYY-XXXX

Test Methodology

• Pipeline build id: xxxx

[SumitJenaHCL]

Verified the ICU version mismatch from #17161 is resolved with this build : https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1130209&view=results

Reproduced the issue's check against the rebuilt nodejs-24.14.1-4.azl3 + nodejs-full-i18n-24.14.1-4.azl3 RPMs on linux/amd64:

Intl.Segmenter now initializes cleanly — no more U_FILE_ACCESS_ERROR: ... contains icudt78l.dat. Binary (ICU 78) and -full-i18n data file (icudt78l.dat) are consistent on amd64, which was the root cause called out in #17161.

[SumitJenaHCL]

Also verified the segfault repro from #17161 no longer triggers with this build.

Ran the issue's exact TypeSpec reproducer in the OneBranch build image with the rebuilt nodejs-24.14.1-4.azl3 RPMs preinstalled:

Result: tsp compile runs to completion and docker exit: 0 — no more Segmentation fault / exit 139 that the stock image produces on amd64. Repeated 5 runs back-to-back, all clean.

[mayankfz]

BB - https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1130209&view=results
Buddy build passes and the issue has been fixed by the changes.

[kgodara912]

Component version upgrade for nodejs upgrade to 24 to prevent segfaults in particular scenarios. Buddy build is successful. LGTM.