feat(linter/config): allow aliasing plugin names to allow names the same as builtin plugins

[camc314]

fixes https://github.com/oxc-project/oxc/issues/15413

[camc314]

• #15569 👈 (View in Graphite)
• #15571
• 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[bot]]

CodSpeed Performance Report

Merging #15569 will not alter performance

_{Comparing c/11-10-feat_config_enhance_external_plugins_support_with_optional_aliases_and_improve_serialization (5d2f5b9) with main (ba76081)[^unexpected-base]} [^unexpected-base]: No successful run was found on main (8f981bd) during the generation of this report, so ba76081 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report.

Summary

✅ 4 untouched
⏩ 33 skipped[^skipped]

[^skipped]: 33 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.

[connorshea]

My two cents: this makes it a lot more complex to configure the linter with jsPlugins and just generally has the potential to really easily have users screw up their configs.

Which is why I didn't suggest a solution like this in the original issue, but ultimately I understand the need and the idea here. So up to you.