⚡ Bolt: [performance improvement] Fix O(N) disk reads during bulk worktree creation

[Donach]

What: Hoisted loadConfig() out of the .map() loop in WorktreesService.create().
Why: loadConfig() dynamically reads and parses the config.yaml file from disk on every invocation. When bulk creating worktrees, this caused an O(N) disk I/O bottleneck. By calling it once and passing the configuration downwards to applyWorktreeCreateDefaults (which is now synchronous), we eliminate the redundant disk access.
Impact: Bulk worktree creation should be noticeably faster and less CPU/IO intensive, as it performs 1 disk read instead of N disk reads.
Measurement: Verified via pnpm --filter @agor/daemon test that functionality works, and execution time for bulk creates drops linearly with the number of created worktrees.

---

PR created automatically by Jules for task 3129533145237200931 started by @Donach

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