⚡ Bolt: Add in-memory caching to SearchTool.deep

[thirdbase1]

💡 What: Implemented a Map-based in-memory cache for SearchTool.deep that checks for previous results inside the core engine's execution loop.
🎯 Why: Agentic loops frequently execute identical queries. Bypassing expensive and redundant network operations significantly improves performance during execution iterations.
📊 Impact: Expected to reduce execution times on redundant loops from ~500ms to <1ms per tool invocation.
🔬 Measurement: Verify cache hit logs (⚡ Cache hit for query) in console output during test execution.

---

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