fix(rome_formatter): fix format range

[denbezrukov]

Summary

1. Fix format issues with incorrect replace rage in the source text.

• crates/rome_js_formatter/tests/specs/js/module/range/range_parenthesis_after_semicol.js.snap
• crates/rome_js_formatter/tests/specs/js/module/range/range_parenthesis_after_semicol_1.js.snap

2. Introduce <<<ROME_RANGE_START>>> and <<<ROME_RANGE_END>>> for snapshot testing.
3. Fix format the range issue if we get a token in the transformed tree.

UPD:

Let say we want to format with range range = 5..94 this code:

a?.b
const a = () => {sdasdsa;
	kek;
	dsad<<<ROME_RANGE_START>>>sa;
	123;
	("y̆es");
};
console.log("🚀".length);
		<<<ROME_RANGE_END>>>
("Jan 1, 2018 – Jan 1, 2019");

We need to calculate source and dest ranges.

• source range we use to find a position in the source text where we need to replace the substring.
• dest range we use to get the substring from the formatted code that we need to replace in the source text.

The example has a problem for the right end. We get the result:

a?.b
const a = () => {
	sdasdsa;
	kek;
	dsadsa;
	123;
	("y̆es");
};
console.log("🚀".length);

( <--- the problem
		
("Jan 1, 2018 – Jan 1, 2019");

it has the following source map:

   ...
    SourceMarker {
        source: 93,
        dest: 96,
    },
    SourceMarker {
        source: 94,
        dest: 97,
    },
    SourceMarker {
        source: 94,
        dest: 99,
    },
    SourceMarker {        <----- Now we take this range.
                                 Because we have a condition `marker.source <= prev_marker.source`
        source: 94,
        dest: 100,       <----- here
    },
    SourceMarker {   <---- But we need to take this one.
        source: 99,     
        dest: 100,       <----- and here
    },
    SourceMarker {
        source: 133,
        dest: 133,
    },
    ...

We can solve the issue by checking markers with the same dest but a greater source.

The same logic we can apply for a left side.

Test Plan

cargo test

Documentation

• The PR requires documentation
• I will create a new PR to update the documentation

[netlify]

✅ Deploy Preview for docs-rometools canceled.

Built without sensitive environment variables

Name	Link
🔨 Latest commit	8407dd9
🔍 Latest deploy log	https://app.netlify.com/sites/docs-rometools/deploys/640d72c81194170007200611

[denbezrukov]

Note:
Need to check in another PR:

a?.b
const a = () => {sdasdsa;
	kek;
	dsadsa;
	123;
	("y̆es");
};
console.log("🚀".length);
("Jan 1,<<<ROME_RANGE_START>>> 201<<<ROME_RANGE_END>>>8 – Jan 1, 2019");123

[MichaReiser]

Could you extend the summary to explain what the root cause is? It would help me with reviewing the changes.

[MichaReiser]

Looks good and thanks for fixing it ! Range formatting and source maps are 🤯