refactor(linter): Replace lazy_static with std::sync::LazyLock for better dependency management

[Copilot]

Summary

This PR improves dependency management by replacing the lazy_static crate with std::sync::LazyLock from the standard library, which has been stable since Rust 1.80.0.

Changes Made

• Replaced lazy_static! macro usage in crates/oxc_macros/src/declare_all_lint_rules.rs with std::sync::LazyLock::new()
• Removed lazy_static dependency from crates/oxc_linter/Cargo.toml
• Cleaned up workspace dependencies by removing lazy_static from the main Cargo.toml
• Updated cargo-shear ignore list to remove lazy_static

Benefits

• ✅ Eliminates external dependency: Reduces total dependency count by removing lazy_static
• ✅ Uses standard library: LazyLock is now part of the standard library (stable since Rust 1.80.0)
• ✅ Maintains performance: LazyLock has equivalent or better performance characteristics
• ✅ Reduces build time: Fewer external dependencies to compile
• ✅ Future-proof: No risk of external crate maintenance issues

Compatibility

This change is safe because:

• OXC currently uses Rust 1.86.0, which is well above the minimum 1.80.0 requirement for LazyLock
• The API is functionally equivalent to lazy_static!
• No runtime behavior changes

Testing

• ✅ just check passes - all compilation successful
• ✅ just fmt passes - no unused dependencies detected
• ✅ oxlint --version works correctly
• ✅ All existing functionality preserved

Before/After Example

Before:

lazy_static::lazy_static! {
    pub static ref RULES: Vec<RuleEnum> = vec![
        // rules...
    ];
}

After:

pub static RULES: std::sync::LazyLock<Vec<RuleEnum>> = std::sync::LazyLock::new(|| vec![
    // rules...
]);

This change aligns with modern Rust practices by leveraging standard library features over external dependencies where possible, contributing to a leaner and more maintainable dependency tree.

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

[graphite-app]

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• 0-merge - adds this PR to the back of the merge queue
• hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

[codspeed-hq]

CodSpeed Instrumentation Performance Report

Merging #12822 will not alter performance

_{Comparing copilot/fix-7f451565-9a3a-40ab-a2b1-4e8628ede16e (348753f) with main (13f0658)}

Summary

✅ 34 untouched benchmarks