feat: support for nested ignore files

[ematipico]

Summary

Closes #2312

This PR enables Biome to read and understand nested .gitignore files, and eventually ignore them in CLI and LSP.

In order to achieve that, I applied the following refactors:

• created a new ExtensionHandler that understands ignore files.
• updated DocumentFileSource, and added a new function called can_read. This function is used in the following places
  • Inside open_file_internal. We bail if Biome can't read a certain file
  • Inside can_handle of the traverse.rs file. Now Biome won't throw an error if it can read a file
• Changed the type of Document::syntax, inside the workspace server. This type holds the content a file, and its parsed tree. Now, the parsed tree is a Option, because a file can be read from disk, but can't be parsed. This the case for ignore files.
• The VCS configuration is now mapped into a new type called VcsSettings. These settings are used to query if a file is ignored.
• The WorkspaceServer now has a new method called update_project_ignore_files, which is in charge of updating the project Settings::vcs_settings with the ignore files that were discovered after the project was scanned. This method does what the former method did: read the file from disk, and create a Gitignore type. As per the new feature, we now have a root Gitignore, the ignore file found in the project's root. Then we have a list of Gitgnore, which represents the nested ignore files; these are different because they must be matched against the folder they are contained to, so they are treated differently.

Test Plan

We have very similar tests that were repeated across CLI commands, I removed them and placed them inside the cases/ folder, using the TemporaryFs, which should help with the testing.

I also tested it manually using our own repository. I did remove dist/ from the ignore file, and added a new .gitignore inside the tailwind package. The CLI correctly ignores the file inside the dist/ folder (created upon compilation). I also checked that VSCode, upon file opening, doesn't provide diagnostics and doesn't format the files. Fortunately the logs are helpful and I could see that the file was ignored.

[siketyan]

Some dbg! and println! calls are not removed? 👀

[ematipico]

Some dbg! and println! calls are not removed? 👀

Addressed, I had the commit not pushed. Thank you!

[github-actions]

Parser conformance results on

js/262

Test result	main count	This PR count	Difference
Total	50387	50387	0
Passed	49072	49072	0
Failed	1315	1315	0
Panics	0	0	0
Coverage	97.39%	97.39%	0.00%

jsx/babel

Test result	main count	This PR count	Difference
Total	40	40	0
Passed	37	37	0
Failed	3	3	0
Panics	0	0	0
Coverage	92.50%	92.50%	0.00%

symbols/microsoft

Test result	main count	This PR count	Difference
Total	6638	6638	0
Passed	2229	2229	0
Failed	4409	4409	0
Panics	0	0	0
Coverage	33.58%	33.58%	0.00%

ts/babel

Test result	main count	This PR count	Difference
Total	798	798	0
Passed	704	704	0
Failed	94	94	0
Panics	0	0	0
Coverage	88.22%	88.22%	0.00%

ts/microsoft

Test result	main count	This PR count	Difference
Total	18655	18655	0
Passed	14306	14306	0
Failed	4349	4349	0
Panics	0	0	0
Coverage	76.69%	76.69%	0.00%

[codspeed-hq]

CodSpeed Performance Report

Merging #5195 will not alter performance

_{Comparing chore/multiple-ignores (08b771a) with main (43601b2)}

Summary

✅ 97 untouched benchmarks

[arendjr]

Nice!

[siketyan]

Looks good to me, thank you for the great improvement 🚀

[arendjr]

Just two last comments 👍