⚡ Bolt: Implement in-memory caching for SearchTool

[thirdbase1]

💡 What: Implemented an in-memory cache (Map) in SearchTool.deep().
🎯 Why: Agentic loops frequently query the exact same context. Without caching, this introduces a significant bottleneck due to redundant simulated network calls (or real ones in the future).
📊 Impact: Reduces latency by 100% on cache hits by instantly returning previous query results.
🔬 Measurement: Run npm run test to verify no regressions in current functionality and confirm standard ExecutionResult wrapping remains intact for cached hits.

---

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