⚡ [Performance] Avoid expensive frame calculations in addIndicator loop

[jhurt]

💡 What: Replaced dynamic property accesses to pageCircle.frame.size.width within the addIndicator loop with a pre-calculated mathematical equivalent based on the predefined radius property.

🎯 Why: Accessing frame.size.width on an SKShapeNode forces an expensive recalculation of its bounding box. Doing this repeatedly within a loop creates unnecessary overhead and stalls layout rendering. By substituting it with radius * 2.0, the visual outcome remains identical while bypassing the performance penalty completely.

📊 Measured Improvement: We were unable to explicitly benchmark this change because the development environment lacks the required Swift/Xcode CLI tools needed to compile or execute Swift benchmarks. However, avoiding SpriteKit bounding box calculations during loops is a widely accepted rendering optimization, reducing CPU overhead during indicator initialization.

---

PR created automatically by Jules for task 2595776754777107726 started by @jhurt

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