feat(linter): implement vitest/prefer-strict-boolean-matchers rule

[baevm]

This PR adds vitest/prefer-strict-boolean-matchers rule.
Passes all original tests with added extra tests for cases like this: expect(value)["toBeFalsy"]();

issue #4656

[baevm]

@codex code review

[codspeed-hq]

Merging this PR will not alter performance

✅ 4 untouched benchmarks
⏩ 52 skipped benchmarks¹

---

_{Comparing baevm:prefer-strict-boolean-matchers (580d952) with main (9a622c7)²}

Footnotes

1. 52 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

2. No successful run was found on main (532c921) during the generation of this report, so 9a622c7 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 580d952403

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[camc314]

thank you!