Disable ETW Logger prior to branch point

I have ~2 more CLs to land before this feature is ready for release.
I suspect that this won't be before M88 branch point so I am disabling
the feature and will re-enable it once we can control it via the
registry in a follow-up CL.  This way, if the required CLs don't land
before branch point, the host is still in a releasable state w/o
requiring any merges.

Change-Id: I03ec977f563679d6b4b84fa6fbbdf849d185e36b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2532924
Commit-Queue: Jamie Walch <jamiewalch@chromium.org>
Auto-Submit: Joe Downing <joedow@chromium.org>
Reviewed-by: Jamie Walch <jamiewalch@chromium.org>
Cr-Commit-Position: refs/heads/master@{#826357}

remoting/host/daemon_process_win.cc

@@ -245,7 +245,8 @@ std::unique_ptr<DaemonProcess> DaemonProcess::Create(
       caller_task_runner, io_task_runner, std::move(stopped_callback));
 
   // Initialize our ETW logger first so we can capture any subsequent events.
-  daemon_process->StartEtwLogging();
+  // TODO(joedow): Re-enable after we can control logging via the registry.
+  // daemon_process->StartEtwLogging();
 
   daemon_process->Initialize();