feat(cli): add --only and --skip options

[Conaclos]

Summary

This PR renames --rule into --only and adds a new option --skip.
These two options can be repeated and used together.
When used together, --skip takes precedence over --only (like --ignore takes precedence over include).

For example, the following command executes only the suspicious/noDebugger rule and all the rules of the style group, but skips the style/useNamingConvention rule.

biome lint --only=suspicious/noDebugger --only=style --skip=style/useNamingConvention

Using skip on a group, skip all rules in the group.
Conversely, using --only on a group, enable all rules of the group - even the ones explicitly disabled in the configuration.

Limitations

Using --only disables the diagnostics about unused suppression comments.
Ideally, we should also filter these diagnostics according to the enabled rules.
However, I don't know how to filter them based on that criteria.

Test Plan

I added tests and updated previous tests.

[codspeed-hq]

CodSpeed Performance Report

Merging #2947 will not alter performance

_{Comparing conaclos/rule-filter (0221b06) with conaclos/rule-filter (3ba4a5f)}

Summary

✅ 92 untouched benchmarks

[github-actions]

Parser conformance results on

js/262

Test result	main count	This PR count	Difference
Total	49701	49701	0
Passed	48721	48721	0
Failed	980	980	0
Panics	0	0	0
Coverage	98.03%	98.03%	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	6322	6322	0
Passed	2036	2036	0
Failed	4286	4286	0
Panics	0	0	0
Coverage	32.20%	32.20%	0.00%

ts/babel

Test result	main count	This PR count	Difference
Total	662	662	0
Passed	593	593	0
Failed	69	69	0
Panics	0	0	0
Coverage	89.58%	89.58%	0.00%

ts/microsoft

Test result	main count	This PR count	Difference
Total	17646	17646	0
Passed	13441	13441	0
Failed	4205	4205	0
Panics	0	0	0
Coverage	76.17%	76.17%	0.00%

[ematipico]

When used together, --skip overrides --only.

I gave my explanation on Discord, I will copy it too here:

Regarding the precedence, I think we should be consistent with what we have already. --only and --skip can be seen as the pair ignore/include, where skip -> ignore and only -> include . We document that ignore takes precedence over include, so we should do the same here.

[Conaclos]

We don't need to call match_group because this check is already handled in filter.match_rule. Thus, I removed this useless check.

[Conaclos]

The implementation of match_group was bogus.

[ematipico]

Great work @Conaclos! This is going to be a great feature 🔥