feat: update node.js unsafe versions for 2026-01-13 security releases (#284)

Node.js published security releases on December 15, 2025 for active
release lines (20.x, 22.x, 24.x, 25.x).

**Updated to secure versions:**
- Node.js 20: `20.19.4` → `20.20.0`
- Node.js 22: `22.17.1` → `22.22.0`
- Node.js 24: `24.4.1` → `24.13.0`
- Node.js 25: Added `25.3.0`

**Preserved existing entries:**
- Node.js 18: Kept at `18.20.6` (January 2025 release)
- Node.js 23: Kept at `23.11.1` (May 2025 release)

All updated entries reference:
https://nodejs.org/en/blog/vulnerability/december-2025-security-releases

The repository maintains entries for all Node.js versions, including EOL
versions, to ensure users are warned about unsafe versions regardless of
which Node.js version they're using.

<!-- START COPILOT ORIGINAL PROMPT -->



<details>

<summary>Original prompt</summary>

> 
> ----
> 
> *This section details on the original issue you should resolve*
> 
> <issue_title>Node.js Monday, December 15, 2025 Security
Releases</issue_title>
>
<issue_description>https://nodejs.org/en/blog/vulnerability/december-2025-security-releases
> 
> Time to say goodbye to Node.js v18</issue_description>
> 
> ## Comments on the Issue (you are @copilot in this section)
> 
> <comments>
> </comments>
> 


</details>



<!-- START COPILOT CODING AGENT SUFFIX -->

- Fixes #283

<!-- START COPILOT CODING AGENT TIPS -->
---

💡 You can make Copilot smarter by setting up custom instructions,
customizing its development environment and configuring Model Context
Protocol (MCP) servers. Learn more [Copilot coding agent
tips](https://gh.io/copilot-coding-agent-tips) in the docs.

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: fengmk2 <156269+fengmk2@users.noreply.github.com>

Author: Copilot

package.json

@@ -75,25 +75,29 @@
         "version": "18.20.6",
         "reason": "https://nodejs.org/en/blog/vulnerability/january-2025-security-releases"
       },
-      ">= 20.0.0 < 20.19.4": {
-        "version": "20.19.4",
-        "reason": "https://nodejs.org/en/blog/vulnerability/july-2025-security-releases"
+      ">= 20.0.0 < 20.20.0": {
+        "version": "20.20.0",
+        "reason": "https://nodejs.org/en/blog/vulnerability/december-2025-security-releases"
       },
       ">= 21.0.0 < 21.7.2": {
         "version": "21.7.2",
         "reason": "https://nodejs.org/en/blog/vulnerability/april-2024-security-releases/"
       },
-      ">= 22.0.0 < 22.17.1": {
-        "version": "22.17.1",
-        "reason": "https://nodejs.org/en/blog/vulnerability/july-2025-security-releases"
+      ">= 22.0.0 < 22.22.0": {
+        "version": "22.22.0",
+        "reason": "https://nodejs.org/en/blog/vulnerability/december-2025-security-releases"
       },
       ">= 23.0.0 < 23.11.1": {
         "version": "23.11.1",
         "reason": "https://nodejs.org/en/blog/vulnerability/may-2025-security-releases"
       },
-      ">= 24.0.0 < 24.4.1": {
-        "version": "24.4.1",
-        "reason": "https://nodejs.org/en/blog/vulnerability/july-2025-security-releases"
+      ">= 24.0.0 < 24.13.0": {
+        "version": "24.13.0",
+        "reason": "https://nodejs.org/en/blog/vulnerability/december-2025-security-releases"
+      },
+      ">= 25.0.0 < 25.3.0": {
+        "version": "25.3.0",
+        "reason": "https://nodejs.org/en/blog/vulnerability/december-2025-security-releases"
       }
     },
     "unsafe-alinode-versions": {