chore(linter): promote no-unreachable to correctness.

[rzvxa]

Since now there are no known false positives, We might want to promote this rule to correctness for the next release so we can find out about its possible false negatives/positives if any.

Feel free to close this PR if you find it too soon for this.

[graphite-app]

Your org has enabled the Graphite merge queue for merging into main

Add the label “merge” to the PR and Graphite will automatically add it to the merge queue when it’s ready to merge. Or use the label “hotfix” to add to the merge queue as a hot fix.

You must have a Graphite account and log in to Graphite in order to use the merge queue. Sign up using this link.

[rzvxa]

• chore(linter): promote no-unreachable to correctness. #3778 👈
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @rzvxa and the rest of your teammates on Graphite

[codspeed-hq]

CodSpeed Performance Report

Merging #3778 will not alter performance

_{Comparing 06-19-chore_linter_promote_no-unreachable_to_correctness (d6f3b76) with main (6ba60e9)}

Summary

✅ 21 untouched benchmarks

[Boshen]

I'll test again when I prepare release for oxlint.

[Boshen]

I manually test and change the rule categories before each release. I raised a few issues. Closing for house keeping.