This deals with some of the "dynamic level control" desires (partially) driving #2.
After this PR, the forwarder will store and return the server's responses back to its client applications. This means that the forwarder's API key can be used to control the logging level of the connected applications.
The future work in #2 will build on this to pass through any API keys supplied by the client, so that level control is per-client, rather than for all clients attached to the same forwarder.
Also updates the lmdb.dll binary that should have been included with the last PR. Until we move to a fully ".NET Core"-esque build (and pack), we'll keep copying the DLL through manually.
This deals with some of the "dynamic level control" desires (partially) driving #2.
After this PR, the forwarder will store and return the server's responses back to its client applications. This means that the forwarder's API key can be used to control the logging level of the connected applications.
The future work in #2 will build on this to pass through any API keys supplied by the client, so that level control is per-client, rather than for all clients attached to the same forwarder.