⚡ Bolt: Optimize HintExtractor by replacing multiple regexes with a single pass loop

[himattm]

💡 What: Replaced multiple string-manipulating regular expressions in HintExtractor.kt with a single manual character iteration loop and a StringBuilder.

🎯 Why: In Kotlin hot paths, relying on multiple regular expressions (e.g., lookarounds for camel case, format validation, whitespace normalization) introduces significant overhead due to state machine compilation and backtracking.

📊 Impact: Reduces CPU cycles and memory allocations significantly during hint extraction by avoiding multiple regex state machine compilations and backtracking overhead, leading to faster execution times.

🔬 Measurement: Run ./gradlew :halogen-engine:test to verify that the extraction logic remains perfectly correct. Profile the execution of HintExtractor.extract to observe the reduced allocation rate and CPU time.

---

PR created automatically by Jules for task 14945420773654845847 started by @himattm

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

[himattm]

Closing this in favor of #74, which curates the parser hot-path changes without the generated .jules/bolt.md metadata and covers the duplicate HintExtractor/SchemaParser optimization work in one PR.

[google-labs-jules]

Closing this in favor of #74, which curates the parser hot-path changes without the generated .jules/bolt.md metadata and covers the duplicate HintExtractor/SchemaParser optimization work in one PR.

Understood. Acknowledging that this work is now obsolete and stopping work on this task.