⚡ Bolt: Implement in-memory caching for deep search tool

[thirdbase1]

💡 What: Implemented an in-memory cache (using a Map) in SearchTool.deep. The cache instantly returns identical query results, wrapping the hit/return logic within this.core.execute() to preserve standard output formatting, logging, and retry logic.
🎯 Why: In agentic loops, repeatedly querying the same external context (like search results) causes an architectural bottleneck due to redundant network requests. This caching mechanism prevents that bottleneck.
📊 Impact: Eliminates completely redundant network requests for previously searched queries, significantly reducing latency and external API load within a single agent session.
🔬 Measurement: Verify by executing the same search query sequentially; the subsequent calls should return almost instantaneously via cache hit without triggering external calls or simulating them. Check logs for "Cache hit for query".

---

PR created automatically by Jules for task 13743546865554436339 started by @thirdbase1

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