Ignore Vitest teardown errors from late container logs

[cristianrgreco]

Summary

The Tests (postgresql, 22.x, docker) job on #1590 failed with all 21 tests passing (log):

EnvironmentTeardownError: [vitest-worker]: Closing rpc while "onUserConsoleLog" was pending
This error originated in "packages/modules/postgresql/src/postgresql-container-snapshot.test.ts" test file.

It is unrelated to that PR's diff. The cause:

• vitest.config.ts sets DEBUG=testcontainers*, and under NODE_ENV=test the logger writes through console.log, which Vitest forwards from the worker to the main process over RPC.
• The worker that creates the reaper follows the reaper container's logs for the life of that worker. Ryuk logs client connected, adding filter and client disconnected for every worker, so a line can arrive after that worker's own test file has finished.
• With --coverage (CI only), the coverage payload is still in flight when a file's tests finish. A console.log sent in that window is still pending when Vitest closes the worker's RPC, and Vitest reports it as an unhandled error (EnvironmentTeardownError: Closing rpc while "onUserConsoleLog" was pending — intermittent on v4/v5, clean on v3, maxWorkers:1 does not help vitest-dev/vitest#11153).

The failed log doesn't show which line was pending. The timing fits: the timescale file finished at 47.8s and the snapshot file at 48.4s.

This adds an onUnhandledError filter that ignores that one error. Reaper logs still stream to testcontainers:containers as before, and no library code changes. The error only carries the RPC method name, so the filter can't be narrowed to reaper lines.

Verification

• Mechanism: a scratch test started an isolated Ryuk and disconnected a second client 1s after the file's tests finished. The client disconnected line was written through console.log in the test worker after the file was done.
• Red: a scratch test file that keeps calling console.log after its test finishes, run with --coverage, exited 1 with the error above in 5/5 runs.
• Green: with this change the same file exited 0 in 5/5 runs.
• Other errors still fail: a scratch test with an unhandled rejection after the file finishes still exits 1.
• npm run format, npm run lint and npm run knip pass.

Not breaking

Test configuration only. Nothing in the published packages changes.