Consider merging in-process-node branch

[Marak]

Currently, all Node.js services are spawned in a new process using the micro-node binary, which is called via microcule.spawn. This ensures process level isolation of the untrusted source code.

Inside micro-node we are using the run-service module, which provides Node.js in-processvm based isolation of the untrusted source code.

Technically ( and previously ) run-service could be executed in-process where microcule.spawn is called ( instead of spawning a new micro-node process ). This could be dangerous as a memory leak or CPU leak in the untrusted source code could affect other running services. It could also be advantageous because it would significantly reduce the amount of resources needed to run Node services, as well as reduce response times by 150+ milliseconds.

We should consider merging the in-process-node branch as a configurable option. Depending on the server environment and intended use-case, being able to spawn in-process Node scripts may be better than enforcing process isolation per Node service.

[Marak]

This will be merged in soon.

I'd like to first setup a good way to run benchmarks before we start exposing optimization options.