Change CompositorFrameSinkSupport creation.

Make the creation of CompositorFrameSinkSupport go through
HostFrameSinkManager. This takes us one step closer to viz architecture
without using Mojo anywhere.

FrameSinkManager is injected into HostFrameSinkManager if we want this
path to be available. Every callsite in the browser process that creates
a CompositorFrameSinkSupport goes through HostFrameSinkManager, with the
exception of Android webview which doesn't use HostFrameSinkManager at
all.

This requires adding a dep from //components/viz/host to
//components/viz/service again. It also requires adding an interface for
DirectLayerTreeFrameSink.

Bug: 742374
Change-Id: I22b9fb855b7a16716dccd4d5233c72412f9b2259
Reviewed-on: https://chromium-review.googlesource.com/570504
Commit-Queue: kylechar <kylechar@chromium.org>
Reviewed-by: Bo Liu <boliu@chromium.org>
Reviewed-by: Fady Samuel <fsamuel@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486795}

diff --git a/ui/aura/BUILD.gn b/ui/aura/BUILD.gn
index 4f937e6d..2d22535 100644
--- a/ui/aura/BUILD.gn
+++ b/ui/aura/BUILD.gn

@@ -143,6 +143,7 @@
     "//components/discardable_memory/client",
     "//components/discardable_memory/public/interfaces",
     "//components/viz/client",
+    "//components/viz/host",
     "//components/viz/service",
     "//gpu/ipc/client",
     "//mojo/public/cpp/system",