feat(organize_imports): support bun:, #, absolute imports

[Conaclos]

Summary

Fix #449.

I added the following categories:

• bun:. Bunjs has recently gained a lot of traction. I think it could be great to handle bun: imports.
  I placed bun: imports just before node:. In this way we have a lexicographic order between bun, node, and npm.
• Absolute imports such as /path.
  I placed it just after the bare specifiers (library imports).
• Node's subpath import #import
  They are placed just after the libraries and just before the relative imports because they generally redirect to a relative path or a library.

I updated the related website page.

I noticed that we recognize implicitly exported node built-in modules as node modules. This contradicts what the documentation says: built-in Node.js modules that are explicitly imported using the node: protocol;. @arendjr what the expected behavior?

Test Plan

Updated tests.

[github-actions]

Parser conformance results on

js/262

Test result	main count	This PR count	Difference
Total	48863	48863	0
Passed	47808	47808	0
Failed	1055	1055	0
Panics	0	0	0
Coverage	97.84%	97.84%	0.00%

jsx/babel

Test result	main count	This PR count	Difference
Total	40	40	0
Passed	37	37	0
Failed	3	3	0
Panics	0	0	0
Coverage	92.50%	92.50%	0.00%

symbols/microsoft

Test result	main count	This PR count	Difference
Total	6212	6212	0
Passed	1767	1767	0
Failed	4445	4445	0
Panics	0	0	0
Coverage	28.44%	28.44%	0.00%

ts/babel

Test result	main count	This PR count	Difference
Total	639	639	0
Passed	571	571	0
Failed	68	68	0
Panics	0	0	0
Coverage	89.36%	89.36%	0.00%

ts/microsoft

Test result	main count	This PR count	Difference
Total	17224	17224	0
Passed	13123	13123	0
Failed	4101	4101	0
Panics	0	0	0
Coverage	76.19%	76.19%	0.00%

[arendjr]

Nice work, thanks!

I think the documentation was slightly off here. Recognizing built-in modules and grouping them with explicit Node imports seems the right thing to do.

Given the philosophy of “grouping imports by distance” I do think it’s a bit odd to put absolute paths before URLs though. I think I would put them just before the relative imports, or the sharp imports, personally. But maybe it even depends on the use case? I don’t use absolute paths myself so I can’t have too strong an opinion 😅

[ematipico]

Thank you for looking after this. Here's some preliminary feedback:

• the PR does refactor and add features, I believe the PR title should enhance the feature instead
• it would be preferable to pull out the refactor from this PR in another PR
• if the previous suggestion can't be done, I would update the PR description and explain the nature of the refactor. "Some code cleanup" isn't sufficient IMHO
• absolute imports should go before relative imports and after libraries, considering that we sort them by "distance from the user"
• Changelog line is missing

[ematipico]

Amazing, great addition! Thank you @Conaclos !