Pipe logs from the virtual interface to the extension through the whist tag

[rebasedming]

Feature Description
Currently protocol logs only exist in the virtual interface and it's really hard to send them to logz.io because we'd need to write our own http request in C++. I tried our old C http request function but it wasn't working, and also tried importing Chromium's http request functions but those are meant for use in the browser process and the virtual interface lives in the renderer process.

A much cleaner implementation is to

1. Have the virtual interface pass each log to the whist element
2. Add an event emitter to the whist element that emits logs
3. Each log is tagged with a unique, incrementing ID
4. All tags broadcast the logs to the extension
5. The extension listens for the logs and uses the logz.io JS API to send the logs up to the server only if the ID is unique (since there can be multiple whist tags at once)