feat(napi/oxlint): run JS plugins on multiple threads

[overlookmotel]

Run JS linter plugins on multiple threads.

WIP. Seems to work - rules are run on JS worker threads in parallel - but effect on performance is not good. In best cases, improvement in perf is not large, and in some cases it's slower than running all JS rules on main thread.

This contrasts steeply against previous multi-threading prototype, where performance scaled well with number of cores. I need to investigate where the bottleneck is.

[overlookmotel]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• feat(napi/oxlint): run JS plugins on multiple threads #13244 👈 (View in Graphite)
• feat(allocator, linter): store worker thread flags in FixedSizeAllocator #13136
• refactor(allocator, linter): add ref counter to FixedSizeAllocator #13135
• docs(allocator): correct and expand safety comments on Allocator methods #13139
• main

---

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.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[codspeed-hq]

CodSpeed Instrumentation Performance Report

Merging #13244 will not alter performance

_{Comparing 08-19-feat_napi_oxlint_run_js_plugins_on_multiple_threads (3ac3b7a) with 08-14-feat_allocator_store_worker_thread_flags_in_fixedsizeallocator_ (317698d)}

Summary

✅ 34 untouched benchmarks

[Boshen]

Close as stale.