⚡ Bolt: [performance improvement] Eliminate O(N) GC pressure in AdaptiveCacheEngine eviction

[LeanBitLab]

💡 What:

Replaced the functional collection pipeline (store.filter { ... }.minByOrNull { ... }) inside AdaptiveCacheEngine.trimToCapacity's while loop with an explicit, allocation-free for loop. Additionally, removed an ambiguous duplicate Role import in MinimalButton.kt that was causing compilation warnings/errors during testing.

🎯 Why:

In Kotlin, invoking .filter on a Map eagerly allocates and populates a new LinkedHashMap. Inside a while loop driving a cache eviction process, this causes $O(N)$ temporary objects to be created and discarded on every single iteration. This generates massive unnecessary Garbage Collection (GC) pressure, slowing down the eviction process and potentially causing frame drops if the cache is trimmed on the main thread or heavily contended.

📊 Impact:

• Zero temporary allocations per eviction loop iteration (down from generating complete Map copies).
• $O(1)$ space complexity for finding the minimum eviction candidate instead of $O(N)$.
• Substantially reduced GC churn during cache trimming.

🔬 Measurement:

• Verify that cache evictions happen instantly without stuttering the UI when capacity is reached.
• Monitor memory profiling during cache saturation: the number of transient LinkedHashMap allocations during trimming will drop to zero.
• Run ./gradlew test to ensure functionality remains identical and all tests pass (which they do).

---

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