feat(rome_js_formatter): import sorting

[ematipico]

Summary

This PR adds a experimental logic to the formatter to sort the import statements inside a module.

The logic is based on some assumptions:

• bare imports, meaning things are like import "polyfill" are not safe, meaning they have side effects;
• the rest of the imports are safe, meaning they are side effects free;

The feature is behind a feature flag.

Test Plan

I created few tests, where we handle different statements, line breaks and cases of premature ending of the statements.

[github-actions]

Parser conformance results on ubuntu-latest

js/262

Test result	main count	This PR count	Difference
Total	45878	45878	0
Passed	44938	44938	0
Failed	940	940	0
Panics	0	0	0
Coverage	97.95%	97.95%	0.00%

jsx/babel

Test result	main count	This PR count	Difference
Total	39	39	0
Passed	36	36	0
Failed	3	3	0
Panics	0	0	0
Coverage	92.31%	92.31%	0.00%

ts/babel

Test result	main count	This PR count	Difference
Total	588	588	0
Passed	519	519	0
Failed	69	69	0
Panics	0	0	0
Coverage	88.27%	88.27%	0.00%

ts/microsoft

Test result	main count	This PR count	Difference
Total	16257	16257	0
Passed	12391	12391	0
Failed	3866	3866	0
Panics	0	0	0
Coverage	76.22%	76.22%	0.00%

[github-actions]

Playground for commit 3eb66d9

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Pages

Latest commit:	856035b
Status:	✅  Deploy successful!
Preview URL:	https://df893d28.tools-8rn.pages.dev

View logs

[MichaReiser]

We'll need to figure out if we indeed want the sorting to be part of the formatter or if it's rather something that should happen inside of the linter. The main issue with doing it inside of the formatter is that it isn't a 100% safe operation, it can change the semantic of the program and this may not be something that the formatter should do.

However, we can provide this as a refactor and allow users to (maybe even by default) opt in to run the sorting on safe.