⚡ Optimize MicrotubuleTorus rendering with InstancedMesh

[jason420247]

💡 What: Refactored the MicrotubuleTorus component in components/QuantumScene.tsx to use THREE.InstancedMesh instead of rendering individual <mesh> components.

🎯 Why: Rendering thousands of individual meshes (360 + 720 = 1,080 in the default scene) is extremely expensive in terms of draw calls and CPU overhead for matrix calculations. Using InstancedMesh allows WebGL to render all instances of the same geometry and material in a single draw call.

📊 Measured Improvement:

• Draw Calls: Reduced from 1,080 to 2 for the toruses in the scene.
• Memory/CPU: Used a reusable THREE.Object3D for matrix updates within the useFrame loop, significantly reducing object allocation and garbage collection pressure during animations.
• Correctness: Added key={count} to the instancedMesh to ensure the component correctly remounts and reallocates the instance buffer if the count prop changes.

---

PR created automatically by Jules for task 11345072046500851492 started by @jason420247

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.