valid-type: use type checking to determine test name type?

[JoshuaKGoldberg]

I noticed that the valid-title rule doesn't use typed linting to determine whether a title is a string (or, pending #247, a function). It just goes off the AST node type. That means dynamic nodes such as Identifiers will always be detected as non-strings:

let nameBase = "My name: ";

const makeName = (suffix: string) => `first ${suffix}`;

describe(makeName("second"), () => { /* ... */ } /*
~~~~~~~~ */
// Test title must be a string.

What is your viewpoint on enabling typed linting (https://typescript-eslint.io/developers/custom-rules#typed-rules)? It would be a breaking change for existing users and have configuration (https://typescript-eslint.io/linting/typed-linting#specifying-tsconfigs / https://typescript-eslint.io/linting/typed-linting/monorepos) & performance (https://typescript-eslint.io/linting/typed-linting#how-is-performance) implications. But I think this is effectively a blocker for #247?

Note that we recommend against rules "progressively enhancing" with type information (except if there's an explicit option): typescript-eslint/typescript-eslint#7440 -> typescript-eslint/typescript-eslint#7440 (comment)

[so1ve]

If these rules requires type information, this will become a breaking change. I prefer implementing it in a separate plugin. (Maybe eslint-plugin-vitest-typechecked? :P)

[veritem]

I don't think it should be necessary a different package. I feel like if we bump another version people will stick to whatever they like. Josh, I'll look into this over fall break.

[so1ve]

Maybe introduce a new option "typecheck"?