⚡ Fix unsafe map iteration in ForEachService

[sudorandom]

💡 What: Modified ForEachService in private/registry/registry.go to hold RLock() throughout the map iteration instead of copying the map reference and iterating unlocked.

🎯 Why: Iterating over a Go map concurrently with additions (e.g. from addService) without a lock causes runtime panics. Assigning the map under the lock (services := r.services) only copied the reference, meaning the unlocked iteration was still iterating the original map data. Holding the RLock() during iteration resolves the safety issue without allocations.

📊 Measured Improvement: No performance degradation and 0 extra memory allocations were added. Creating a slice alternative would have added ~16KB per call in large registries, but by deferring RUnlock(), performance remained identical to the baseline (both map iterations) while achieving thread-safety. Included benchmarks in private/registry/registry_bench_test.go to verify these numbers.

---

PR created automatically by Jules for task 4973022860422588748 started by @sudorandom

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