fix(pool): avoid --require argument when running in deno

[pi0]

Description

This is a hotfix for Deno runtime not supporting --require argument and broken in latest vitest v4 (but i guess is safe fix as deno does not emit such warns anyway)

Resolves #8896

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

• It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
• Ideally, include a test that fails without this PR but passes with it.
• Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.
• Please check Allow edits by maintainers to make review process faster. Note that this option is not available for repositories that are owned by Github organizations.

Tests

• Run the tests with pnpm test:ci.

Documentation

• If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

• Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.

[AriPerkkio]

I'm really not fan of adding runtime checks for NodeJS compatibility for other runtimes. We don't do this for Bun either. Ideally this should be fixed in Deno.

Though this is such a small change that I'm not strongly against it.