mock framer-motion to fix jest unit test fails (#2362)

Author: rudransh-shrivastava

frontend/jest.setup.ts

@@ -27,6 +27,15 @@ if (typeof global.fetch === 'undefined') {
   } as Response)
 }
 
+// Mock framer-motion due to how Jest 30 ESM resolution treats
+// motion-dom's internal .mjs imports as "outside test scope".
+jest.mock('framer-motion', () => {
+  return {
+    ...jest.requireActual('framer-motion'),
+    LazyMotion: ({ children }) => children,
+  }
+})
+
 jest.mock('next-auth/react', () => {
   return {
     ...jest.requireActual('next-auth/react'),

frontend/package.json

@@ -81,7 +81,7 @@
     "@tailwindcss/postcss": "^4.1.14",
     "@testing-library/jest-dom": "^6.9.1",
     "@testing-library/react": "^16.3.0",
-    "@types/jest": "^29.5.14",
+    "@types/jest": "^30.0.0",
     "@types/leaflet": "^1.9.20",
     "@types/leaflet.markercluster": "^1.5.6",
     "@types/markdown-it": "^14.1.2",
@@ -103,7 +103,7 @@
     "globals": "^16.4.0",
     "identity-obj-proxy": "^3.0.0",
     "import-in-the-middle": "^1.14.4",
-    "jest": "^29.7.0",
+    "jest": "^30.2.0",
     "jest-axe": "^10.0.0",
     "jest-environment-jsdom": "^30.2.0",
     "open": "^10.2.0",