Prepare independent rules for ESLint removal

[gonzaloriestra]

WHY are these changes introduced?

Oxlint's native rules leave gaps in the existing CLI lint conventions. Prepare replacements before removing ESLint in #8211.

WHAT is this pull request doing?

Add independent JavaScript rules for naming, member and import ordering, workspace boundaries, unused imports, public API documentation, and core/Node conventions. Parse TSDoc directly. Focused tests cover these rules, including an Oxlint integration test that rejects loading ESLint or its upstream plugins.

This intermediate PR keeps the existing compatibility adapter and ESLint pass active. The final PR activates the independent rules and removes that dependency tree. The independent replacements cover repository conventions, with limitations documented in #8211; they do not reproduce every upstream option or behavior.

Enable the JSON-output command rule, preserve generated-file exemptions, and retain the public plugin exports. Keep the security emitter's exemption while compatibility remains active. Preserve generated import spacing and enable array formatting so regeneration matches the committed files. Normalize the integration test’s Node preload path for Windows, including paths with spaces. Run plugin tests in separate processes and serialize their files on Windows to limit native-buffer memory use. Run Nx plugins in-process in the integration test so detached workers cannot keep its temporary directory locked on Windows. Retry temporary-directory cleanup after child processes exit.

Validation

Full lint, frozen installation, and all 92 plugin tests passed. Uncached GraphQL generation leaves no generated-file changes. All 77 plugin tests also pass in the final ESLint-free setup. All non-e2e GitHub Actions checks pass, including the Windows test matrix.

Checklist

• I've considered possible cross-platform impacts (Mac, Linux, Windows)
• I've considered possible documentation changes
• I've considered analytics changes to measure impact
• The change is user-facing — I've identified the correct bump type and added a changeset