⚡ Bolt: [performance improvement] Concurrent execution for non-batched Weaver operations

[ishaanxgupta]

💡 What: Optimized src/pipelines/weaver.py to process non-batched vector operations (temporal, code, snippet) concurrently using asyncio.gather instead of awaiting them sequentially in a for loop.

🎯 Why: Non-batched vector operations involve network/I/O wait times (e.g., adding nodes/edges to Neo4j). Awaiting these sequentially creates a linear performance degradation O(N). Concurrency solves this bottleneck.

📊 Impact: This change dramatically reduces execution latency for non-batched ops. A benchmark executing 10 simulated db ops of 0.1s each went from 1.0s (sequential) to 0.1s (concurrent).

🔬 Measurement: Benchmarks and logs of execution time verify this improvement.

---

PR created automatically by Jules for task 9922097411374336866 started by @ishaanxgupta

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