refactor(rome_cli): file process

[ematipico]

Summary

I finally had a breakthrough! It took me a bit to arrive there, but I finally managed to breakdown the logic of the files and re-use it when needed.

There were two significant issues:

• the logic of processing a file lived in one single file, and that logic needed to consider different scenarios. This wasn't ideal because adding new logic causes more burden, and it's challenging to get it right without breaking the existing behaviour;
• it was difficult to move code around due to the lifetime constraints we have;

I created a new wrapper called SharedTraversalOptions. This tiny struct is used to make the compiler happy and tell it that "ctx is just borrowed, and it won't escape the boundaries of the lifetimes".

I created a new WorkspaceFile, another tiny wrapper meant to coordinate the writing of a new file. For example, when applying fixes to a file, we need to:

• write the new contents to disk;
• update the CST of the file we have in the workspace;

This must be done because when we pass to the formatting pass, we need to apply the format, we need to have the new content of the file at end, even for the diagnostics.

I will look into it later if it's possible to optimize this part. Unfortunately, we need to keep a String around (it was like this before too).

This is a BREAKING CHANGE because now formatting diagnostics are always shown when running rome check. If you noticed, many snapshots were updated, offering more diagnostics. This is the intended feature of the rome check command.

Test Plan

I updated the existing tests and made sure that the emitted messages are correct.

[netlify]

✅ Deploy Preview for docs-rometools canceled.

Name	Link
🔨 Latest commit	4e2dd48
🔍 Latest deploy log	https://app.netlify.com/sites/docs-rometools/deploys/64a429c0ac0d4100078dae1c