inspector: implement sub process inspection.

[eugeneo]

This is an umbrella bug for implementing the functionality outlined here - nodejs/diagnostics#77

This implementation will land in several stages. Current plan is as follows:

• Custom inspector message dispatcher. This stage will allow extending the Inspector protocol beyond domains provided by the V8
• Provide Node.js implementaion for the Target protocol as outlined here
• Provide communication channel between Node.js instances that runs outside the regular event loop (akin to Inspector WS server). This is necessary so the child instances are still accessible while the head instance is busy or is suspended on a breakpoint.
• Integrate with process.fork and process.spawn, if possible. This will make debugging child processes easier.

[eugeneo]

For the item#3 (communication channel) the proposal is to introduce a new command line flag --inspector-pipe=path/to/pipe so parent process can communicate with child processes without child process listening on a socket. Pipe IO will be using same thread that is currently used for the inspector WS server.

[eugeneo]

Pull request to check first two check boxes: #16629

[TimothyGu]

This should also make it (more) possible to implement inspector for workers (ayojs/ayo#58).

[eugeneo]

Chrome protocol has a major limitation that it relies on the parent target to outlive the children (as it is true in Web Platform use-case). This limitation greatly reduces usability in the Node.js case, which, coupled with amount of changes required in a platform, greatly reduces appeal. We are working on an alternative approach prototype.

[boneskull]

@eugeneo Is this effort tracked publicly anywhere?