feat(oxlint/lsp): support jsPlugins

[Sysix]

related #14826

[Sysix]

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(oxlint/lsp): support jsPlugins #15839 👈 (View in Graphite)
• chore(oxlint/napi): add createWorkspace & destroyWorkspace js callback function #16121
• 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 Performance Report

Merging #15839 will not alter performance

_{Comparing 11-18-draft_oxlnt_lsp_support_jsplugins_ (62ed619) with 11-25-chore_oxlint_napi_add_createworkspace_destroyworkspace_js_callback_function (ce53742)¹}

Summary

✅ 4 untouched
⏩ 41 skipped²

Footnotes

1. No successful run was found on 11-25-chore_oxlint_napi_add_createworkspace_destroyworkspace_js_callback_function (8a4ded6) during the generation of this report, so 4d1596f was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

2. 41 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[Sysix]

@overlookmotel I am not sure if this is the right approach.
When changing a .oxlintrc.json file, the server will restart the tool (linter) and re-register all plugins.
I would prefer that each instance get started with an empty registeredPluginPaths, and not share between restarts/workspaces.
But it looks complicated to achieve :(

The main difference from oxlint with jsPlugins and oxlint --lsp is:

• oxlint will only run once with a known cwd from the beginning
• oxlint --lsp will start multiple instances for each workspace (see https://code.visualstudio.com/docs/editing/workspaces/multi-root-workspaces for multi root workspaces)
• oxlint --lsp will restart the linter (service) when a .oxlintrc.json file or a relevant LSP configuration is changed