[Feature] Add complexity checking to Oxlint preset for feature parity with Biome

[itaymendel]

Is your feature request related to a problem? Please describe.

Inconsistency in complexity checking. The Biome preset includes noExcessiveCognitiveComplexity:20 to catch overly complex functions, but the Oxlint preset has no equivalent complexity rules. This means users choosing Oxlint lose an important code quality check.

For teams standardizing on Oxlint, this creates a gap where complex, hard-to-maintain functions can slip through. Exactly the kind of issue a zero-config preset should catch.

Describe the solution you'd like

Add an oxc-complexity-plugin to the Oxlint core configuration. This would give users consistent code quality guarantees regardless of toolchain choice.
The plugin is production-ready (v1.0.0), tested, and integrates directly with Oxlint's plugin system.

Full disclosure: I maintain this plugin, but I believe the feature parity issue exists regardless of the implementation. I'm open to alternative solutions if there's a better way to bring complexity checking to the Oxlint preset.

Describe alternatives you've considered

1. Wait for oxlint to add native complexity rules - no timeline for this
2. Document the gap - defeats the "zero-config" value proposition
3. Remove complexity checking from Biome preset - reduces code quality
4. Add to individual projects - creates configuration overhead that Ultracite aims to eliminate