Add performance monitoring to launcher's osquery runtime

[marpaia]

As a result of #95, we disabled osquery's watchdog functionality in #103. The underlying reason WHY the extension wouldn't start up is because when the launcher starts an osquery instance, a fake shell binary is launched as the extension. The launcher itself then registers with the osqueryd process, providing the plugins. When osqueryd restarts itself, it relaunches the extension binary, but since this is just a shell binary, the launcher has no way of knowing to re-register the extension plugins. Thus, we disable the watchdog, since it does nothing but harm the health of the instance. As a result of this, however, we need to add our own performance checks and logging to the launcher to ensure that osquery stays well-behaved.

[directionless]

Note: This was never implemented, and may not make sense. This it was closed)