feat(node): add child_process.fork

[kt3k]

This PR implements child_process.fork in std/node

This implements at least the basic feature of fork and enabled the basic test cases (child-process-spawn-node.js).

This doesn't implement ipc features. So I commented out ipe-related assertion in the test cases.

The diff might look big, but that is because this PR moves ChildProcess class from node/child_process to node/internal/chil_process to follow the internal structure of Node.js code base.

closes #1690

[kt3k]

The CI is blocked by #1694

[bartlomieju]

@kt3k is this ready? I don't see any new method in the chil_process.ts file.

[kt3k]

@bartlomieju This should add fork method. Please see the last line of node/child_process.ts. BTW now we have two child_process.ts files in node/ and node/internal/.

[bartlomieju]

Thanks @kt3k I was looking at the wrong file. This API is gonna be tricky due to flags, but this is good progress

[bartlomieju]

Why is location argument needed?

[kt3k]

Some npm module does something like typeof location to detect the environment and causes uncaught errors. So giving --location avoids those errors, but that probably should be solved by denoland/deno#12969

Ok. I'll remove this option as a first pass

[bartlomieju]

Yeah, let's address it in Deno directly

[bartlomieju]

Yeah... this is problematic, ideally we'd use the same permissions as the parent process, but unfortunately we don't have access to these flags.

[kt3k]

Oh, because we use deno run --compat for spawning subcommand, the subprocess have to use [email protected] for std/node and which still includes BINARY notation in enum..

[bartlomieju]

Unfortunately I don't see a good way to fix it at the moment, as deno.land/std/ doesn't allow to link to main branch

[bartlomieju]

LGTM

[bartlomieju]

This is a good workaround for now