fix(formatter,oxfmt): Handle css-in-js comment inside template

[leaysgur]

Fix the bug found in https://github.com/oxc-project/oxc/blob/605de80b541b8d85e5129ab620eae63ed07a6a1e/apps/oxfmt/conformance/snapshots/diffs/xxx-in-js-comment/comment-inside.js.md

[leaysgur]

• fix(formatter,oxfmt): Handle css-in-js comment inside template #20452 👈 (View in Graphite)
• feat(formatter,oxfmt): Support /* LANG */ comment for gql|html-in-js #20224
• 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 changes, fast-track this PR to the front of the merge queue

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]

Merging this PR will not alter performance

✅ 49 untouched benchmarks
⏩ 7 skipped benchmarks¹

---

_{Comparing 03-17-fix_formatter_oxfmt_handle_css-in-js_comment_inside_template (f2ec84b) with 03-11-feat_oxfmt_support___lang___comment_for_gql_html-in-js (605de80)}

Footnotes

1. 7 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. ↩

[Dunqing]

Merge activity

• Mar 17, 2:57 PM UTC: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Mar 17, 2:57 PM UTC: Dunqing added this pull request to the Graphite merge queue.
• Mar 17, 3:44 PM UTC: Merged by the Graphite merge queue.