Linter: Migrate `run_on_jest_node` to `run` implementations

Currently, all (or most) Jest/Vitest lint rules use the custom run_on_jest_node methods. These methods do not benefit from our AST type optimizations and also make the core linter code just a little bit more complicated. We should migrate these rules to all use the run methods so that they can benefit from the AST node type optimizations and we can simplify the core linter code to be more streamlined.

Rough plan:

1. Migrate all current Jest/Vitest rules to use run instead of run_on_jest_node (can be done incrementally)
2. Update all current rules to use should_run method instead of the custom should_run_on_jest_node (can be done incrementally)
3. Remove the run_on_jest_node and associated code

Start by locating the current run_on_jest_node and should_run_on_jest_node implementations and the Jest/Vitest rules that use them. Migrate those rules to run and should_run incrementally, then remove the old methods and associated core code; done means no current rules depend on the custom methods.