Fail more gracefully on partially Node.js compatible runtime environments

Some JavaScript runtime environments have limitations/assumptions, for example:

"Node.js APIs are available under the node: prefix, and this prefix must be used when importing modules, both in your code and the npm packages you depend on." https://developers.cloudflare.com/workers/runtime-apis/nodejs/

We could improve support for these environments by failing more gracefully.

For example, when requireing Node.js modules, an alternative "safe require" function could be used that tries e.g. child_process then node:child_process then otherwise returns null. Failure to require a module should probably lead to APIs also returning null.

Ideally we'll be able to add an integration test for this e.g. by running Wrangler "locally" within CI.

See also https://github.com/lovell/detect-libc/pull/24 for some previous discussion.

Start by locating the existing Node.js module require paths and the current CI test entry points. Review the linked detect-libc discussion and test the behavior in a partially Node.js-compatible runtime; done means unsupported module imports fail gracefully and the relevant APIs return null, with an integration test if the CI setup permits it.