Add a timeout for killing osquery process group

[RebeccaMahany]

Relates to #1442

Impose a timeout on running taskkill on Windows; returns error from running taskkill so that it can be logged by the errgroup. 10 seconds seems like a very safe timeout -- in test, taskkill took around 200 ms.

[directionless]

Actually... Can we log something if the context is canceled? Or maybe that will be in the err anyhow

[RebeccaMahany]

@directionless we log the returned error here: https://github.com/kolide/launcher/blob/main/pkg/osquery/runtime/runner.go#L434

In test (reducing the timeout to 10ms to force a timeout), that log looks like this for me:

{"caller":"runner.go:437","err":"exit status 1","level":"info","msg":"killing osquery process","session_pid":12832,"ts":"2023-11-30T18:54:27.4700033Z"}

Let me update the error with more information.

[RebeccaMahany]

@directionless updated, log looks like this in the case of timeout now:

{"caller":"runner.go:437","err":"running taskkill: context err: context deadline exceeded, err: exit status 1","level":"info","msg":"killing osquery process","session_pid":6092,"ts":"2023-11-30T19:12:20.7923216Z"}

And here's what it looks like with a taskkill error:

{"caller":"runner.go:437","err":"running taskkill: output: ERROR: Invalid argument/option - '/QQQ'.\r\nType \"TASKKILL /?\" for usage.\r\n, err: exit status 1","level":"info","msg":"killing osquery process","session_pid":6024,"ts":"2023-11-30T19:17:55.5194436Z"}