fix(js): add --forceExit to Jest to prevent test hang with Node 24

Jest 30 with Node 24 waits indefinitely for open handles (timers,
promises) that the WebSocket mock tests don't properly clean up.
Adding --forceExit forces Jest to exit after tests complete.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Author: thjaeckle

javascript/lib/api/package.json

@@ -33,7 +33,7 @@
     "build:barrels:copyright-header": "eslint -c ../../eslint.config.js --quiet --fix dist/index.ts",
     "build:barrels:compile": "tsc --project tsconfig-barrels.json",
     "lint": "eslint .",
-    "test": "jest",
+    "test": "jest --forceExit",
     "test:watch": "jest --watch"
   },
   "keywords": [

javascript/lib/dom/package.json

@@ -31,7 +31,7 @@
     "build:barrels:copyright-header": "eslint -c ../../eslint.config.js --fix dist/index.ts",
     "build:barrels:compile": "tsc --project tsconfig-barrels.json",
     "lint": "eslint .",
-    "test": "jest",
+    "test": "jest --forceExit",
     "test:watch": "jest --watch"
   },
   "keywords": [

javascript/lib/node/package.json

@@ -39,7 +39,7 @@
     "build:barrels:copyright-header": "eslint -c ../../eslint.config.js --quiet --fix dist/index.ts",
     "build:barrels:compile": "tsc --project tsconfig-barrels.json",
     "lint": "eslint .",
-    "test": "jest",
+    "test": "jest --forceExit",
     "test:watch": "jest --watch"
   },
   "keywords": [