fix(ci): fix cross-realm ArrayBuffer issue in Node 20 JSDOM tests

- Upgrade CI Node.js from 20 to 22 (Active LTS) to fix JSDOM cross-realm
  ArrayBuffer rejection by Web Crypto API
- Always override globalThis.crypto with Node's native webcrypto in
  setupTests.ts to avoid JSDOM's partial crypto implementation

Author: pankaj-bind

.github/workflows/ci.yml

@@ -122,7 +122,7 @@ jobs:
       - name: Set up Node.js
         uses: actions/setup-node@v4
         with:
-          node-version: '20'
+          node-version: '22'
           cache: npm
           cache-dependency-path: frontend/package-lock.json
 

frontend/src/setupTests.ts

@@ -27,14 +27,13 @@ import { webcrypto } from 'crypto';
 // @ts-ignore - Node.js util module
 import { TextEncoder, TextDecoder } from 'util';
 
-// Polyfill globalThis.crypto for Node.js environment
-if (typeof globalThis.crypto === 'undefined') {
-  Object.defineProperty(globalThis, 'crypto', {
-    value: webcrypto,
-    writable: false,
-    configurable: false
-  });
-}
+// Polyfill globalThis.crypto with Node's native webcrypto
+// This avoids JSDOM cross-realm ArrayBuffer issues with Web Crypto API
+Object.defineProperty(globalThis, 'crypto', {
+  value: webcrypto,
+  writable: true,
+  configurable: true
+});
 
 if (typeof globalThis.TextEncoder === 'undefined') {
   (globalThis as { TextEncoder: typeof TextEncoder }).TextEncoder = TextEncoder;

frontend/src/utils/__tests__/encryption.test.ts

@@ -1,8 +1,4 @@
 // src/utils/__tests__/encryption.test.ts
-/**
- * @jest-environment node
- */
-
 /**
  * Client-Side Encryption Unit Tests
  * ═══════════════════════════════════════════════════════════════════════════════