Execute each handler in a separate process (like we do for Rust)

[Konard]

This can be optional behavior that can be switched on/off. May be even configurable on per handler basis.

This also will allow to isolate entire logs of handler execution from other handlers.

And it will much easier to use TS translation in a separate process.

May be useful to solve:

• Plain eval is used without transpilation. Ts handlers do not work #19
• Add possibility to see logs of handler run #34
• Add possibility to debug by using breakpoints #33

If this issue is done, there will be no real need for #4

This also may solve issues with absence of stack trace inside eval.

This will also make handling of handlers truly multithreaded.

Direct remote debugging will also be much easier.

It will also increase the overall stability of handlers, meaning no single handler can kill all others by unhandled exception.

[FreePhoenix888]

Do you mind if I take this?

[Konard]

@FreePhoenix888 it is now yours, please make it in a separate pull request, and give it for review to me before merge. And let's do it step by step. As small steps as possible. Stability and backward compatibility is the highest priority.