feat(linter): add support for vitest/valid-title rule

[taearls]

I noticed that there's already a fully working implementation of jest/valid-title, and the logic is very similar. However, the vitest rule has slightly different configuration options, so it's not quite the same. I made the vitest/valid-title rule work with their specific configuration options and unit tests.

As part of this, I added support for the vitest typecheck option so that all the vitest-specific test scenarios would pass for this rule. This meant adding a VitestPluginSettings module with typecheck available as a boolean, defaulting to false.

I considered trying to reuse some of the logic from the jest rule equivalent, but since there are subtle differences I didn't think the refactor was worth it on a first pass. The only tradeoff is that there's some duplicate logic between the jest / vitest rules for this.

Future consideration: The only other rule that uses typecheck as a config setting in eslint-plugin-vitest is the expect-expect rule, which we currently have listed in the VITEST_COMPATIBLE_JEST_RULES. It might be worth adding support for typecheck in that rule for 100% compatibility.

---

Reference:

Vitest Config Options from vitest/valid_title.rs):

interface Options {
    ignoreTypeOfDescribeName?: boolean;
    allowArguments?: boolean;
    disallowedWords?: string[];
    mustNotMatch?: Partial<Record<'describe' | 'test' | 'it', string>> | string;
    mustMatch?: Partial<Record<'describe' | 'test' | 'it', string>> | string;
}

Jest Config Options (from jest/valid_title.rs):

interface Options {
    ignoreSpaces?: boolean;
    ignoreTypeOfTestName?: boolean;
    ignoreTypeOfDescribeName?: boolean;
    disallowedWords?: string[];
    mustNotMatch?: Partial<Record<'describe' | 'test' | 'it', string>> | string;
    mustMatch?: Partial<Record<'describe' | 'test' | 'it', string>> | string;
}

Vitest valid-title Rule Docs
Jest valid-title Rule Docs

[codspeed-hq]

CodSpeed Instrumentation Performance Report

Merging #12085 will not alter performance

_{Comparing taearls:linter/vitest-valid-title (461e23f) with main (d732e85)}

Summary

✅ 38 untouched benchmarks

[camc314]

Thanks for this PR, jest/vitest rules are mapped together as theyua re often so similar. Assuming there isn't a lot of extra work, could you move the test cases from this file into the jest.valid_title.rs?

[taearls]

Sure! Would it also make sense to combine these rules into one file, merging the configurations? Or should I just move the tests?