⚡ Bolt: move git fetch outside PR conflict resolution loop

[Cylae]

💡 What:

Moved git fetch origin $BaseBranch outside the conflict resolution helper function Resolve-AndUpdate and placed it before the main PR processing loop.

🎯 Why:

Previously, Resolve-AndUpdate fetched origin/$BaseBranch over the network on every PR that encountered a merge conflict. Network I/O is expensive (typically 200ms-1s+ per call). Fetching once upfront prior to processing PRs ensures the local repository has the latest base branch refs for all conflict resolutions in the run without repeating network round-trips.

📊 Impact & Measurement:

• Baseline: $N$ network git fetch calls for $N$ conflicting PRs.
• Optimized: 1 network git fetch call per script run.
• Improvement: Saves $(N - 1)$ network round-trips per run (e.g., saving ~$1-5$s when processing 5-10 conflicting PRs).

---

PR created automatically by Jules for task 10984374079893272468 started by @Cylae

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