Bolt: Optimize array filtering allocations in count aggregations

[georgi]

What

Replaced multiple array .filter(...).length checks with a single O(N) loop to compute category counts in usePackageManager and dependent task counts in parsePlanDocument.

Why

When extracting metrics or counts from arrays, iterating via .filter(...) creates an intermediate array solely to read its length. When done multiple times over the same array (e.g., getting counts for different status categories), it creates an O(K*N) performance bottleneck and scales poorly due to garbage collection pressure from intermediate array allocations.

Impact

Reduces the time complexity of category counting in package manager from O(3*N) to O(N) and prevents unnecessary array allocations on high-frequency UI updates. Similarly reduces task processing overhead when parsing plan documents.

Verification

Ran npm run test targeting the affected packages src/components/chat/message/ and src/components/packages/. Verified that parsePlanDocument and usePackageManager pass all behavior tests. Ran npm run typecheck and npm run lint:design.

---

PR created automatically by Jules for task 5615517030902977173 started by @georgi

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