Record all log lines, and don't let logging alter the test run

[LukeButters]

Background

An issue exists in which recording trace logs appears to:

• Not record all log lines, since logging can be done in parallel and this results in an exception when two threads write to the same file.
• That exception would bubble out of the sink, although maybe something catches it before it throws an exception in halibut.
• Appeared to alter the timings of test causing some web-socket tests to fail. (Which is probably a real bug?)

Results

Logging is now done to a queue, which is async written to disk. This means:

• We don't throw exceptions in the sink.
• Writing logs is thread safe.
• Each log line written does not open, write to, and close a file which should stop changing the timings of tests and improve performance/decrease disk IO.

The queue is used over a lock to avoid logging introducing a hidden lock which could cause code to become dependent on the lock.

How to review this PR

Quality :heavy_check_mark:

Pre-requisites

• [ ] I have read How we use GitHub Issues for help deciding when and where it's appropriate to make an issue.
• [ ] I have considered informing or consulting the right people, according to the ownership map.
• [ ] I have considered appropriate testing for my change.

[LukeButters]

@borland points out it might make more sense to use a serilog file sink. That probably would make more sense, since I suspect we could just write directly to the artifact's folder and it looks like it supports buffering so maybe everything is done out of the critical I am not sure. Talking to @acodrington he found that the serilog file sinks didn't do exactly what we needed, "since we need a sink that can handle multiple files".