⚡ Optimize canTypeWord to avoid array allocation

[timbornemann]

💡 What: Replaced word.split('').every(...) with a standard for loop using index access in canTypeWord.
🎯 Why: The original implementation created a new array for every word check, causing unnecessary memory allocation and GC overhead.
📊 Measured Improvement:

• Baseline: ~1199ms for 1,000,000 iterations.
• Optimized: ~1036ms for 1,000,000 iterations.
• Improvement: ~13.5% speedup.
• Correctness: Verified that behavior remains identical for mixed case and special characters.

---

PR created automatically by Jules for task 13101909043133478898 started by @timbornemann

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