⚡ Bolt: [performance improvement] Eliminate eager array allocations in UI and Memory modules

[acebytes]

💡 What: Replaced eager .filter calls with where clauses in loops and .lazy.filter sequences in counting/sorting operations, and added code comments explaining the optimization.\n🎯 Why: To avoid unnecessary intermediate array allocations, reducing memory churn and improving execution performance.\n📊 Impact: Reduces memory overhead and garbage generation during frequent UI updates and scheduled memory scans.\n🔬 Measurement: Profile the application with Instruments (Allocations instrument) to observe reduced transient array allocations during normal execution.

---

PR created automatically by Jules for task 17477173474139026306 started by @acebytes

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