Currently, we have the concept of "Vitest compatible" where the Jest rules act as if they were also Vitest rules. This does save on the amount of code that needs to be written, but it is confusing. It makes the linter more complex, because it adds a lot of special casing to the tooling.

As a result, we have a number of bugs related to these "Vitest compatible" rules:

• linter: --rules omits vitest equivalents of shared jest/vitest rules #20466
• linter: Support optional message argument in Vitest valid-expect rule #18851
• linter: valid_describe_callback should not execute in Vitest #9060
• linter: confusing error message for vitest plugin #13019

I propose that we:

• Move each Vitest compatible Jest rule in VITEST_COMPATIBLE_JEST_RULES to an additional new Vitest rule
• Once all rules are migrated, remove the VITEST_COMPATIBLE_JEST_RULES array

In addition, we will also want to do as part of this:

• Update documentation for the new Vitest rules to be Vitest-specific, start removing references to Jest.
• Allow configuration to be automatically generated (using JsonSchema)

Rules to convert:

• consistent-test-it
• expect-expect
• max-expects
• max-nested-describe
• no-alias-methods
• no-commented-out-tests
• no-conditional-expect
• no-conditional-in-test
• no-disabled-tests
• no-duplicate-hooks
• no-focused-tests
• no-hooks
• no-identical-title
• no-interpolation-in-snapshots
• no-large-snapshots
• no-mocks-import
• no-restricted-jest-methods (note that this one will require cleaning up crates/oxc_linter/src/disable_directives.rs and crates/oxc_linter/src/config/rules.rs to remove special-casing due to this rule having a different name in vitest vs jest. And make sure the vitest rule name is no-restricted-vi-methods)
• no-restricted-matchers
• no-standalone-expect
• no-test-prefixes
• no-test-return-statement
• no-unneeded-async-expect-function
• prefer-called-with
• prefer-comparison-matcher
• prefer-each
• prefer-equality-matcher
• prefer-expect-resolves
• prefer-hooks-in-order
• prefer-hooks-on-top
• prefer-lowercase-title
• prefer-mock-promise-shorthand
• prefer-mock-return-shorthand
• prefer-snapshot-hint
• prefer-spy-on
• prefer-strict-equal
• prefer-to-be
• prefer-to-contain
• prefer-to-have-been-called-times
• prefer-to-have-length
• prefer-todo
• require-hook
• require-to-throw-message
• require-top-level-describe
• valid-describe-callback
• valid-expect
• valid-expect-in-promise
• valid-title