⚡ Perf: Optimize O(N*M) loop in Heatmap component

[artosien]

💡 What: Optimized the number frequency lookup inside the Heatmap component by implementing a Map wrapped in useMemo.
🎯 Why: The previous implementation used an O(N) .find() array search inside an O(M) mapping loop, resulting in an O(N*M) time complexity. Since this happens on every render and during interactions, it creates unnecessary CPU overhead. Converting it to a Map enables O(1) lookups, dropping the time complexity to O(N+M).
📊 Measured Improvement: In a standalone benchmark simulating the lookup process (100,000 iterations), the baseline .find() approach took ~313.671ms while the optimized Map.get() approach took only ~30.971ms. This represents roughly a 10x measurable performance improvement for this code path.

---

PR created automatically by Jules for task 2174890813040324969 started by @artosien

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