fix: apply --skip-parse-errors to lint, check and ci commands

[unvalley]

Summary

Closes #3859
This PR applies the --skip-parse-errors option to below commands.

• biome lint
• biome check
• biome ci

biome format is already applied the option.

Since there is no need to display parse errors in analyze and format respectively, parse errors in format executed later are not output as messages (commented in code).

Test Plan

Added snapshot test

[unvalley]

do nothing if already skipped parse error on the analyze phase.

[ematipico]

I'm wondering if we should rename this flag. I introduced this option at the very beginning, when there was only a formatter. Now the meaning of "error" is different, and now there's a linter too.

What do you think?

[unvalley]

@ematipico

Here’s the current description of --skip-errors:

–skip-errors — Skip files with syntax errors instead of emitting an error diagnostic.

Because the flag only deals with parse errors, how about renaming it to --skip-parse-errors?

I’d also suggest making it a sub-command option rather than a global one. Commands like lint, format , check , and ci need it, but the others don’t.

PS: rethink, we don't need to make it a specific options for them, I leave it as a global option.

[ematipico]

--skip-parse-errors seems good!

[unvalley]

@ematipico Can we include the renaming to v2.0.0 release? (Assuming I make that change in this PR)
If so, I think we can rename --skip-errors to --skip-parse-errors without the deprecation phase.

[ematipico]

Can we include the renaming to v2.0.0 release?

Yes, that was the idea :)

[codspeed-hq]

CodSpeed Performance Report

Merging #5780 will not alter performance

_{Comparing unvalley:use-skip-errors (78ed2dd) with main (5f321a9)}

Summary

✅ 95 untouched benchmarks