Make everything use active evals (#30)

* Add trace log level

* Use active eval to implement spdlog

* Split server/client active eval interfaces

Since all properties are *not* valid on both sides

* +200% fire resistance

* Implement exec using active evaluations

* Fully implement child process streams

* Watch impl, move child_process back to explicitly adding events

Automatically forwarding all events might be the right move, but wanna
think/discuss it a bit more because it didn't come out very cleanly.

* Would you like some args with that callback?

* Implement the rest of child_process using active evals

* Rampant memory leaks

Emit "kill" to active evaluations when client disconnects in order to
kill processes. Most likely won't be the final solution.

* Resolve some minor issues with output panel

* Implement node-pty with active evals

* Provide clearTimeout to vm sandbox

* Implement socket with active evals

* Extract some callback logic

Also remove some eval interfaces, need to re-think those.

* Implement net.Server and remainder of net.Socket using active evals

* Implement dispose for active evaluations

* Use trace for express requests

* Handle sending buffers through evaluation events

* Make event logging a bit more clear

* Fix some errors due to us not actually instantiating until connect/listen

* is this a commit message?

* We can just create the evaluator in the ctor

Not sure what I was thinking.

* memory leak for you, memory leak for everyone

* it's a ternary now

* Don't dispose automatically on close or error

The code may or may not be disposable at that point.

* Handle parsing buffers on the client side as well

* Remove unused protobuf

* Remove TypedValue

* Remove unused forkProvider and test

* Improve dispose pattern for active evals

* Socket calls close after error; no need to bind both

* Improve comment

* Comment is no longer wishy washy due to explicit boolean

* Simplify check for sendHandle and options

* Replace _require with __non_webpack_require__

Webpack will then replace this with `require` which we then provide to
the vm sandbox.

* Provide path.parse

* Prevent original-fs from loading

* Start with a pid of -1

vscode immediately checks the PID to see if the debug process launch
correctly, but of course we don't get the pid synchronously.

* Pass arguments to bootstrap-fork

* Fully implement streams

Was causing errors because internally the stream would set this.writing
to true and it would never become false, so subsequent messages would
never send.

* Fix serializing errors and streams emitting errors multiple times

* Was emitting close to data

* Fix missing path for spawned processes

* Move evaluation onDispose call

Now it's accurate and runs when the active evaluation has actually
disposed.

* Fix promisifying fs.exists

* Fix some active eval callback issues

* Patch existsSync in debug adapter

packages/protocol/src/proto/client.proto

@@ -1,22 +1,9 @@
 syntax = "proto3";
-import "command.proto";
 import "node.proto";
 import "vscode.proto";
 
 message ClientMessage {
 	oneof msg {
-		// command.proto
-		NewSessionMessage new_session = 1;
-		ShutdownSessionMessage shutdown_session = 2;
-		WriteToSessionMessage write_to_session = 3;
-		CloseSessionInputMessage close_session_input = 4;
-		ResizeSessionTTYMessage resize_session_tty = 5;
-		NewConnectionMessage new_connection = 6;
-		ConnectionOutputMessage connection_output = 7;
-		ConnectionCloseMessage connection_close = 8;
-		NewServerMessage new_server = 9;
-		ServerCloseMessage server_close = 10;
-
 		// node.proto
 		NewEvalMessage new_eval = 11;
 		EvalEventMessage eval_event = 12;
@@ -25,20 +12,6 @@ message ClientMessage {
 
 message ServerMessage {
 	oneof msg {
-		// command.proto
-		NewSessionFailureMessage new_session_failure = 1;
-		SessionDoneMessage session_done = 2;
-		SessionOutputMessage session_output = 3;
-		IdentifySessionMessage identify_session = 4;
-		NewConnectionFailureMessage connection_failure = 5;
-		ConnectionOutputMessage connection_output = 6;
-		ConnectionCloseMessage connection_close = 7;
-		ConnectionEstablishedMessage connection_established = 8;
-		NewServerFailureMessage server_failure = 9;
-		ServerEstablishedMessage server_established = 10;
-		ServerCloseMessage server_close = 11;
-		ServerConnectionEstablishedMessage server_connection_established = 12;
-	
 		// node.proto
 		EvalFailedMessage eval_failed = 13;
 		EvalDoneMessage eval_done = 14;