fix: force single luma.gl@9.3 via resolutions, update lockfile

deck.gl@9.2.x ships luma@9.2.x as a dep causing two luma instances at
runtime. Add yarn resolutions to force all @luma.gl/* to 9.3.0-alpha.2
so deck.gl and community modules share a single luma instance.

All 61 node tests passing with deck.gl@9.2.10 + luma.gl@9.3.0-alpha.2.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: charlieforward9

package.json

@@ -67,6 +67,14 @@
     "vitest": "^4.0.18",
     "vitest-browser-react": "^2.0.5"
   },
+  "resolutions": {
+    "@luma.gl/constants": "~9.3.0-alpha.2",
+    "@luma.gl/core": "~9.3.0-alpha.2",
+    "@luma.gl/engine": "~9.3.0-alpha.2",
+    "@luma.gl/shadertools": "~9.3.0-alpha.2",
+    "@luma.gl/webgl": "~9.3.0-alpha.2",
+    "@luma.gl/webgpu": "~9.3.0-alpha.2"
+  },
   "packageExtensions": {
     "deck.gl@*": {
       "peerDependenciesMeta": {
@@ -75,6 +83,16 @@
         }
       }
     },
+    "@deck.gl/*@*": {
+      "peerDependencies": {
+        "@luma.gl/constants": ">=9.2.6",
+        "@luma.gl/core": ">=9.2.6",
+        "@luma.gl/engine": ">=9.2.6",
+        "@luma.gl/shadertools": ">=9.2.6",
+        "@luma.gl/webgl": ">=9.2.6",
+        "@luma.gl/webgpu": ">=9.2.6"
+      }
+    },
     "zod-to-json-schema@*": {
       "peerDependencies": {
         "zod": "^4.0.0"