⚡ Optimize Regex compilation in extractJsonData

[EchoOfMaridia]

💡 What:
Moved the compilation of several complex Regex instances out of the extractJsonData function and into a private file-level list jsonExtractionPatterns.

🎯 Why:
The extractJsonData function is designed as a fallback parser that scans for key-value pairs using several regular expressions. Previously, the listOf(Regex(...), ...) block was instantiated and compiled upon every single invocation of the function, which scales poorly when handling large payloads or running the extraction repeatedly. Compiling regular expressions is an expensive operation that only needs to happen once.

📊 Measured Improvement:
A focused benchmark was created (JsonExtractBenchmarkTest) to measure the performance of 10,000 extractions of heavily malformed JSON.

• Baseline: ~27,684 ms / 10,000 iterations
• After Optimization: ~26,268 ms / 10,000 iterations
• Overall Impact: A slight measurable improvement within tight synthetic benchmarking environments. However, the real value lies in the reduction of unneeded object allocations (Regex and Matcher states) across production executions, avoiding unnecessary Garbage Collection pressure as the JIT compiler doesn't always manage to inline/eliminate array allocations in complex Regex matchers out in the wild.

---

PR created automatically by Jules for task 3174988498822496703 started by @EchoOfMaridia

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