fix: report active test on device timeout

[mrousavy]

Summary

When the host-side runTests(file) bridge RPC times out, include the last app-side test that emitted test-started but has not emitted test-finished yet.

This keeps the existing DeviceNotRespondingError behavior, but makes timeout failures actionable for long-running native Promise hangs. Instead of only reporting that the whole test file did not respond, Jest output can now include the active test name.

Test

• corepack pnpm exec vitest run --config vite.config.ts src/__tests__/execute-run.test.ts from packages/jest

[vercel]

@mrousavy is attempting to deploy a commit to the Callstack Team on Vercel.

A member of the Team first needs to authorize it.

[V3RON]

Closing as superseded by #138. That PR now reports runtime test and suite-hook timeouts directly from the runtime, includes pending promise diagnostics, and restarts the app after timeout cleanup.