Windows event logs at debug level

[directionless]

Chatting with a customer, they point out a couple of odd things:

https://github.com/kolide/launcher/blob/9bf773782d2c7834c9a1bb7244b4f0b6595c4763/cmd/launcher/svc_windows.go#L36 happens before the logs are leveled. This creates a weird case where people get one thing called "debug" in their info logs.

https://github.com/kolide/launcher/blob/1e7be612e3c038c14be50cc0857feaa8c68fa1ff/pkg/log/eventlog/writer_windows.go#L51 forces everything to the info stream. This seems wrong. We could probably parse the log and send it tagged correctly.

As long as we're there, we could probably also remove the duplicative "level=xx" parameter.