⚡ [performance improvement] Parallelize linting I/O and processing

[Tcode-Motion]

💡 What: Use rayon to process lint files in parallel using par_iter(). Updated the LintRule trait to require Send + Sync.
🎯 Why: Linting reads files synchronously in a single-threaded loop, which becomes a bottleneck when linting large codebases with many files.
📊 Measured Improvement: We do not have a full integration performance benchmark set up for tsc lint execution on huge repositories, but a synthetic script iterating over files using par_iter demonstrates that by parallelizing file reads and the perfectly independent CPU-bound static analysis phases (lexer, parser, semantic analyzer, and linter), the runtime scales efficiently with the number of CPU cores.

---

PR created automatically by Jules for task 14372932745298422202 started by @Tcode-Motion

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