Next release (#584)

* engine: spike mapping console logs to an adaptor logger

* runtime: messy tweak to module loading

* engine,runtime: revert linker change and fix tests

* engine: track test file

* logger: dont stringify json output AND serialize errors

This cause problems with the worker because errors get  flattened to {}, and also we have to double parse.

Now the logger will just emit whatever it logged to whatever the log emmiter is, so JSON stays as JSON. Which is good, but it no longer guarantees it'll be serializable

* logger: tidy

* engine: don't parse json logs coming out of the logger

* engine, worker: better handling of objects coming from the logger

The logger always sends raw json, but the log message is stringified by the engine, and rebuilt by the worker before sending to lightning

this last bit needs work but its better

* engine: fix tests

* logger: tests and types

* cli: update test

* engine: types

* worker: update tests

* logger: set a special json emitter so that json logs get nicely printed in the CLI

* logger: fix types

* logger: log all json to .log

* tests: fixes

* logger: fix tests

* logger: serialise print() properly

* logger: types

* engine: fix logs to gcp

They were neglecting to parse the strings sent out by the new json logger

* test: update log handling

* engine: fix passing test

It was secretly failing under the hood

* runtime: add tests on job logger and errors

* logger: improve detection of error objects

* engine: tests on error logging

* engine: restore adaptor logger

* changesets

* Tidy ups

* engine: refactor log messages (and be a bit more lenient about structure)

* worker: simplify logging

* tiny tidyups

* remove old docs

* version: [email protected]