⚡ Bolt: Refactor TelemetrySystem to use O(1) ring buffer

[dhaatrik]

💡 What: Refactored TelemetrySystem to use a circular array (ring buffer) instead of standard array push() and shift() operations.
🎯 Why: In high-frequency recording loops (like the telemetry data), using Array.prototype.shift() when the buffer exceeds its maxDataPoints causes an O(N) array re-indexing operation, leading to performance degradation and high garbage collection pressure.
📊 Impact: Expected to reduce execution time for telemetry shifting/updating significantly by converting O(N) shift operations to O(1) modulo index assignments. In benchmark tests (benchmark_telemetry.ts and benchmark_telemetry_stress.ts), it shows an improvement in time per operation for worst-case buffer shifting.
🔬 Measurement: Verify by running tests/benchmark_telemetry_stress.ts. Time per iteration should remain stable in O(1) instead of degrading linearly. All telemetry UI and tests should continue to pass normally.

---

PR created automatically by Jules for task 3503670957296995953 started by @dhaatrik

[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.