Sometimes launcher on Windows cannot find a valid osquery executable

[RebeccaMahany]

We see logs on osquery extension startup showing:

1. no osquery updates found
2. the originally installed osquery executable is determined to not be executable: fullBinaryPath not executable. Returning nil
3. launcher attempts to start up osquery with an empty string for the osqueryd path, which does not work

The simplest explanation could be that the timeout is just too short on Windows sometimes (maybe/especially when the system is in modern standby?).

To address this issue:

• We should log the CheckExecutable error in this case, to diagnose why launcher is having this issue: Fully log CheckExecutable failures #1504
• Depending on the results, we should address the issue -- maybe adjusting the timeout for the executable check, or adjusting the check in some other way, or adjusting the osquery extension startup behavior to not require the executable check or to fall back to running the originally-installed osquery executable regardless of check status.

[RebeccaMahany]

Addressed by #1788