refactor(prettier): Refactor IR related macros

[leaysgur]

• Remove format! macro
• Rename string related macros, &'static: text! and 'a: dynamic_text!
• Apply wrap! macro instead of manually using enter|leave_node
• Introduce /ir directory and move Doc, impl Display, DocBuilder, etc.

I'm not yet determined how to, how deep to use macro, but this is first stepping stone... 🥌

[graphite-app]

Your org has enabled the Graphite merge queue for merging into main

Add the label “0-merge” to the PR and Graphite will automatically add it to the merge queue when it’s ready to merge. Or use the label “hotfix” to add to the merge queue as a hot fix.

You must have a Graphite account and log in to Graphite in order to use the merge queue. Sign up using this link.

[leaysgur]

free to make any changes to the oxc_prettier crate.
#5068 (comment)

@Boshen Can I understand this to mean that I can merge PRs without review?

[codspeed-hq]

CodSpeed Performance Report

Merging #7491 will not alter performance

_{Comparing p/clean-up (3a1ef6a) with main (8d89fdc)}

Summary

✅ 30 untouched benchmarks

[Boshen]

how deep to use macro

Although I ban macros in the rest of the codebase, I allow in this crate to make code easier to read.

So the general guideline is:

• make the formatter functions easier to read by making everything shorter and more concise.
• save some key strokes

[Boshen]

free to make any changes to the oxc_prettier crate.
#5068 (comment)

@Boshen Can I understand this to mean that I can merge PRs without review?

Or use graphite to stack the PRs, whatever makes you productive. I can review after merge.

[Boshen]

Merge activity

• Nov 26, 4:27 AM EST: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Nov 26, 4:27 AM EST: A user added this pull request to the Graphite merge queue.
• Nov 26, 4:38 AM EST: A user merged this pull request with the Graphite merge queue.