build: add Navara for the experimental engine

Pins @navaramap/three and @navaramap/three-default-plugin 0.2.1 with
their peers three 0.185.1 and postprocessing 6.39.4 (mapillary-js keeps
its own nested three 0.134). The dev server leaves the Navara packages
and their wasm workers out of dependency pre-bundling so wasm-bindgen
resolves its .wasm next to the package. Nothing imports Navara yet: the
Cesium-mode main chunk is byte-identical (2,837,992 bytes, same hash).

src/tooling/viteBuild.test.mjs

@@ -229,3 +229,16 @@ test('the CSP admits the event media embeds and the Maps JavaScript API, and no
   // X posts load in X's own frames.
   assert.ok(frames.includes('https://platform.twitter.com'));
 });
+
+test('the dev server leaves Navara and its wasm workers out of dependency pre-bundling', () => {
+  const { optimizeDeps } = createBrowserViteConfig({});
+  for (const name of [
+    '@navaramap/three',
+    '@navaramap/three-default-plugin',
+    '@navaramap/engine',
+    '@navaramap/engine-api',
+    '@navaramap/engine-worker',
+    '@navaramap/engine-font-worker',
+  ])
+    assert.ok(optimizeDeps.exclude?.includes(name), name);
+});