⚡ Bolt: Fix N+1 Query in getUserOrders

[fatelessdev]

💡 What: Changed getUserOrders to fetch all order items using a single IN array query rather than calling select on orderItems repeatedly via Promise.all mapping.
🎯 Why: The previous implementation suffered from the N+1 query issue, generating as many SELECT operations on order items as there were total orders for a user.
📊 Impact: Expected to drastically reduce response time and database load by turning O(N) queries into O(1) when fetching order history arrays.
🔬 Measurement: Inspect the getUserOrders usage within the network logs, loading the order history UI should be significantly snappier on users with more than 10 past orders.

---

PR created automatically by Jules for task 14118661806768694130 started by @f4teless

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

[fatelessdev]

🤖 AI Code Review

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

📦 Commits

Analyzing commits...

📂 Files selected for processing

Fetching changed files...

---

Powered by LetsReview