feat: enable CSS linter and CSS formatter

[ematipico]

Summary

This PR enables CSS parsing and CSS formatting.

Important

Internally, we decided that linter and formatting are opt-in and disabled by default. Why? Because it's possible that parser, formatter and linter aren't quite stable yet, and it's hightly possible that there are bugs.

Enabling this in Biome comes with new options across the configuration. Mainly now, each language section can enable or disable the linter. This was required because, until now, we haven't officially had lint rules for languages other than JSON, and that single lint rule still needs some work, that's why it isn't documented yet.

The PR adds:

• javascript.linter.enabled
• css.linter.enabled
• json.linter.enabled

The relative CLI options are also added.

Also, since we are officially enabling the CSS formatter to the people with this PR, I took the chance to remove inde_size from the options. It doesn't make sense to expose an option that is already deprecated.

Technical changes

Most of the changes are around configuration and overrides. It's mostly boilerplate and copying code from other implementations.

One thing of relevance though, is the creation of the type AnalyzerOptions when we do linting. So far, we were using a standalone function to do that, however, that's not the right way not.

Our infrastructure allows to generate generic functions at triat level that return options for a specifict language, for example format_options. These are function meant to receive options from global settings (biome.json and CLI) and the LSP (client options). I did create a new function called analyzer_options, and how each language implements that. The implementation of each function is a copy-paste of their former functions, but adapted to use the proper parameters.

Test Plan

I created new test cases inside a new file called handle_css_files.rs. I find using the "cases" concept better than grouping stuff by commands. More files, sure, but they are smaller and focused on certain things.

[codspeed-hq]

CodSpeed Performance Report

Merging #2790 will not alter performance

_{Comparing chore/css-analyzer (4ed0034) with chore/css-analyzer (ef9364a)}

Summary

✅ 99 untouched benchmarks

[denbezrukov]

Do I understand correctly that we don't even parse a file if we disable linting and formatting?

[ematipico]

Do I understand correctly that we don't even parse a file if we disable linting and formatting?

Exactly, we skip it