Support Rstest static type tests in discovery and run actions #111

Rstest is adding opt-in type tests through typecheck configuration and the instance API/CLI. The implementation is loaded from the optional @rstest/typecheck package, which must match the core version. Type assertions and lightweight static registration APIs are imported from @rstest/typecheck; core registration imports also remain recognized. This tracks the companion editor compatibility work required by the core repository's contribution guidelines.

The implementation discovers *.test-d.ts / *.spec-d.ts files, statically collects direct describe / test / it calls, and runs the project's compiler without executing the test file. listTests({ includeTaskLocation: true }) returns these cases through the existing ListedTest shape. Reporter case results carry meta.typecheck: true; file results additionally carry the checker name and version.

Please cover:

• Discover and run configured type tests through createRstest / listTests / run, including mixed runtime/type projects and typecheck.only.
• Preserve source locations, nested names, and compiler diagnostics. Expression titles are their source text; files without static registrations have a single [typecheck] case.
• Explain that name/file filters select reported cases while the full tsconfig remains checked. .only, .skip, parameterized and conditional registration modifiers are unsupported and produce collection errors.
• Type tests run on the host for browser projects as well. They do not execute setup files, runtime hooks, snapshots, retries, or coverage; editor actions should respect those limits.
• Type testing does not support watch mode. Use one-shot run actions for type cases; the core reports an error for watch plus typecheck.
• Recognize @rstest/typecheck registration imports and preserve actionable missing-package/version-mismatch errors. Ordinary runtime projects do not require this package.
• Verify onlyFailures across mixed runtime/type projects: core shares file failure history and falls back to a full run once no recorded failures remain. Explicit file/name filters take precedence.
• Respect bail results: later type cases and projects are not reported after the run-wide limit; the compiler invocation already started for a project still checks the full tsconfig.
• Include discovery/run/result mapping tests against the core PR build before release.

Core PR: web-infra-dev/rstest#1984