Treat `test.override` like `test.scoped` in rule parsing

[nami8824]

Summary

Vitest 4.1 introduced test.override as the replacement for deprecated test.scoped.

eslint-plugin-vitest already treats test.scoped / it.scoped as fixture configuration APIs rather than test cases in several rules. However, test.override / it.override is not handled the same way yet.

This can cause false positives in rules that inspect test calls, titles, or hook ordering.

Affected rules

• expect-expect

  • Should not require assertions for test.override(...) / it.override(...).

• prefer-hooks-on-top

  • Should not treat test.override(...) / it.override(...) as test cases before hooks.

• valid-title

  • Should not validate test.override(...) / it.override(...) as titled test calls.

• require-top-level-describe

  • Should not treat test.override(...) / it.override(...) as top-level test cases.