⚡ Bolt: Optimize selected results evaluation to avoid eager array allocations

[acebytes]

• 💡 What: Updated selectedSize to use .lazy.filter before .reduce, and replaced !selectedResults.isEmpty in hasSelection with .contains(where: \.isSelected).
• 🎯 Why: hasSelection previously computed the full selectedResults array (allocating intermediate memory) just to check if it was empty. This avoids memory churn, particularly in SwiftUI computed properties evaluated on every render loop.
• 📊 Impact: Eliminates O(N) intermediate array allocations and O(N) iterations for hasSelection by short-circuiting at the first selected item.
• 🔬 Measurement: Verify functionality of the selection logic and memory footprint via Xcode Instruments' Allocations template during multiple select/deselect actions in the UI.

---

PR created automatically by Jules for task 13688548409392173005 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.