Move ResourceUsageReporter to //content.

This is part of an effort to eliminate manifest overlays. (See bug).

This interface actually needs to be hooked up in some utility processes & renderers. At face value it seems like something like this could be part of the service manager API but it turns out to be very blink/v8 specific. Ultimately it should probably be exposed by the blink & proxy resolver services. Due to the way the task manager obtains these APIs currently moving to content makes the most sense.

http://crbug.com/810851

Change-Id: Ic7948d41487120d3207e96b866645854f7405b92
Reviewed-on: https://chromium-review.googlesource.com/887429
Reviewed-by: Tom Sepez <[email protected]>
Reviewed-by: Ken Rockot <[email protected]>
Commit-Queue: Ben Goodger <[email protected]>
Cr-Commit-Position: refs/heads/master@{#535868}
diff --git a/content/renderer/render_thread_impl.h b/content/renderer/render_thread_impl.h
index 7097f21..289e5135 100644
--- a/content/renderer/render_thread_impl.h
+++ b/content/renderer/render_thread_impl.h
@@ -829,6 +829,8 @@
   mojo::Binding<viz::mojom::CompositingModeWatcher>
       compositing_mode_watcher_binding_;
 
+  base::WeakPtrFactory<RenderThreadImpl> weak_factory_;
+
   DISALLOW_COPY_AND_ASSIGN(RenderThreadImpl);
 };