fix: deduplicate three.js instance bundled by jsroot

[remo-lab]

Summary

Fixes #655

JSROOT bundles its own copy of three.js (v174) directly inside
jsroot/modules/three.mjs (~59K lines). This results in a second
three.js instance being loaded at runtime alongside Phoenix's
three.js (v178), triggering the warning:

WARNING: Multiple instances of Three.js being imported.

Having multiple instances of three.js can lead to issues such as:

• memory leaks
• instanceof check failures across module boundaries
• other undefined behavior at runtime

---

Fix

• Added a Yarn resolution in the root package.json to enforce a
  single three@~0.178.0 version across dependencies.

• Added a postinstall patch script
  scripts/patch-jsroot-three.js that replaces JSROOT's inlined
  three.js implementation with a simple re-export:

export * from 'three'

The patch runs automatically during yarn install, ensuring the
fix is applied transparently without requiring any manual steps.

---

Verification

• Confirmed that only one REVISION (178) exists in the bundled
  vendor.js. The duplicate version (174) is no longer present.

• The console warning no longer appears when running Phoenix on
  my localhost. I have attached a video below showing a comparison
  between the official Phoenix demo website and my local
  environment after applying the fix.

Recording.2026-03-07.155825.mp4

[remo-lab]

@EdwardMoyse , I’ve opened this PR to address the duplicate Three.js instance issue. I’ve verified locally that the warning no longer appears. Would really appreciate a review when you have time. Thanks!

[remo-lab]

@EdwardMoyse , shall i update anything on this pr?

[EdwardMoyse]

Thanks very much for this - obviously the preferred solution would be for jsroot to fix this on their side, but in the meantime this seems like a good idea.