⚡ Bolt: Optimize project tasks retrieval latency

[criptogus]

⚡ Bolt: Optimized GET /api/projects/:id/tasks

💡 What:
Modified the GET /api/projects/:id/tasks endpoint to execute database queries concurrently instead of sequentially.

🎯 Why:
The endpoint was performing 3 sequential database round-trips:

1. Check if project exists (1x latency)
2. Count total tasks (1x latency)
3. Fetch tasks page (1x latency)
   Total latency was ~3x DB RTT.

By using Promise.all, we reduce the total latency to ~1x DB RTT (plus minimal overhead).

📊 Impact:

• Measured improvement from 373ms to 139ms in a local benchmark with 100ms artificial DB delay.
• Expected to significantly reduce latency for users, especially those with higher database latency.

🔬 Measurement:
Verified using a temporary benchmark script that mocked the database with fixed delays.

---

PR created automatically by Jules for task 3895850224876953889 started by @criptogus

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