fix: upgrade @hono/node-server to fix Node.js v24 crash

[fede-kamel]

Closes #1604

Summary

• Bump @hono/node-server from ^1.3.3 (resolved 1.13.5) to ^1.14.2 (resolved 1.19.14)
• Fixes Failed to find Response internal state key error on Node.js v24
• One-line change in package.json + lockfile update

Root Cause

Node.js v24 ships a newer version of Undici that changed how Response internal state is accessed (nodejs/undici@45dceeaf). This was fixed upstream in honojs/node-server#241 and released in @hono/node-server@1.14.2.

Before (Node v24)

Failed to find Response internal state key
Failed to start the app: 1

After (Node v24)

🚀 Your AI Gateway is running at:
   http://localhost:8787

✨ Ready for connections!

Test Plan

• npm run build — clean
• node start-test.js — boots without error, exits 0
• Unit tests — no regressions (same 6 pre-existing failures in handlers/services/)

[fede-kamel]

@VisargD @narengogi Verified the fix on Node.js v24.10.0:

Build + server boot:

✅ npm run build — clean (2.8s)
✅ node start-test.js — boots without "Failed to find Response internal state key", exits 0

Unit tests (29/29 pass):

Test Suites: 6 failed, 1 passed, 7 total
Tests:       29 passed, 29 total

The 6 suite failures are pre-existing on main (missing ../hooksService module import) — not related to this change.

TypeScript: same 2 pre-existing errors on main (bytez/api.ts, open-ai-base/index.ts) — not related.

Before (Node v24 + @hono/node-server@1.13.5):

Failed to find Response internal state key
Failed to start the app: 1

After (Node v24 + @hono/node-server@1.19.14):

🚀 Your AI Gateway is running at: http://localhost:8787
✨ Ready for connections!
EXIT: 0

This is a one-line version bump — minimal risk, high impact for anyone developing on Node v24.