Report imported test objects called through unknown members or with a timeout

[Huldoser]

What changed

Comparing the scan with Vitest's own parser on 40 open-source projects found tests missing with no diagnostic in two cases, both through names imported from a module the scan follows:

• A call through a member the scan doesn't know. Effect calls it.effect('…', fn) on the it that @effect/vitest extends, and 4,039 tests in its own repository were missing without a word. A call with a title and a body through a name that reads like a test function is now followed, and reported with unresolved-test-import when it can't be.
• A timeout after the body. trigger.dev calls postgresTest('…', fn, 60_000), which Vitest accepts. Such a call now counts as shaped like a test.

Following @effect/vitest turned up a third problem: its own export const it = internal.it was read as Vitest's it, from export * from 'vitest' in the same module. A module's own export now wins over export *, as in JavaScript.

On the corpus, the Sentry unit tests get 3 more unresolved-test-import errors, for files that use only it.effect, and the real-projects page says 24 instead of 21. Nothing else changes.

Checklist

• Tests cover the change, and npm run coverage reports 100%.
• The docs describe the change: the guide or reference pages, the README, or the TSDoc of exported functions.
• No docs change is needed.
• A changeset describes the change for users (npm run changeset), or the change does not affect them.