GitLab

This is the first CL needed to allow the Windows host to log w/o
logman or sawbuck.  Each process on Windows create an ETW trace
provider with a well-known GUID, this is what logman/sawbuck use
to capture a trace.

With this feature, we will update the Windows host so that its log
output can be redirected (likely to the Windows event log, could
also be a human readable file or ETW file).

In this CL, I am adding the class which is used to enable/disable
ETW tracing.  Future CLs will add the ETW consumer which listens
for the events and the logic needed to parse and redirect the
output to a new location.

Bug: 1144185
Change-Id: I01affb28c01d01bde8649faffaf59a17c8a9cd67
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2509948Reviewed-by: Jamie Walch <jamiewalch@chromium.org>
Commit-Queue: Joe Downing <joedow@google.com>
Cr-Commit-Position: refs/heads/master@{#822868}