⚡ Bolt: Optimize cache eviction loop

[LeanBitLab]

💡 What: Replaced the eager collection operation store.filter { ... }.minByOrNull { ... } with an explicit allocation-free for loop in AdaptiveCacheEngine.trimToCapacity().
🎯 Why: The previous implementation allocated a new map on every iteration of the while loop during cache eviction, causing significant garbage collection pressure.
📊 Impact: Removes O(N) map allocations per evicted item, reducing GC pauses and UI stutters during cache eviction.
🔬 Measurement: Run the test suite (./gradlew test) to verify the engine functions identically. Observe memory allocation profiles during heavy cache eviction.

---

PR created automatically by Jules for task 1680374343001790759 started by @LeanBitLab

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