feat(linter/eslint-plugin-vitest): Implement valid-title eslint rule

[Afsoon]

Related to #4656

Set valid-title as a compatible vitest rule

oxc-project/oxlint-migrate#301

[codspeed-hq]

CodSpeed Performance Report

Merging #17224 will not alter performance

_{Comparing Afsoon:vitest-valid-title (b1ff2de) with main (c8c5341)}

Summary

✅ 4 untouched
⏩ 41 skipped¹

Footnotes

1. 41 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. ↩

[connorshea]

Started a review and then realized that... technically valid-title is already implemented for vitest partially via the jest/valid-title rule? It just wasn't done properly: bd74603

Do we need to do anything specific for that?

[connorshea]

Suggested change

	#[serde(default)]
	#[serde(rename = "vitestImports")]
	#[serde(rename = "vitestImports", default)]

[Afsoon]

@connorshea Looks that not, we have to extend the current valid-title, apart of adding as a compatible vitest rule. Vitest have some test that depends on the vitestImports pattern. I'm going to set this PR as draft and update it when I have time for it.

Thanks!

[Afsoon]

Doing from zero valid-title and warn-todo I have found some issues that are probably better talked before to do anything. The current PR doesn't handle the vitestImports test. The other issue is how vitest and jest are detected.

[Afsoon]

@camc314 I have recovered the changes I made to handle the test with vitestImports settings, and added thoses test in the rule