Move media::mojom::RemoterFactory to content, add ContentBrowserClient API.

chrome/browser/chrome_content_browser_manifest_overlay.json

Index: chrome/browser/chrome_content_browser_manifest_overlay.json
diff --git a/chrome/browser/chrome_content_browser_manifest_overlay.json b/chrome/browser/chrome_content_browser_manifest_overlay.json
index 0f86f193eca496f38a4ed9e27ceff1f4885b41a9..fc3b9a52e80ba55b99f98588a74b8197ddae31fd 100644
--- a/chrome/browser/chrome_content_browser_manifest_overlay.json
+++ b/chrome/browser/chrome_content_browser_manifest_overlay.json
@@ -52,6 +52,7 @@
           "dom_distiller::mojom::DistillerJavaScriptService",
           "extensions::KeepAlive",
           "extensions::mime_handler::MimeHandlerService",
+          "media::mojom::RemoterFactory",

[Ben Goodger (Google), 2016/11/16 03:58:50]

If you're exposing this interface in //content this should be in
//content/public/app/mojo/content_browser_manifest.json not here, otherwise it
won't be exposed to other content embedders.

You would have discovered this if you had a browsertest in content.

[Ben Goodger (Google), 2016/11/16 18:56:13]

Scratch this. Looking at content/public/app/mojo/content_browser_manifest.json,
it looks like this interface is already provided there so this is unnecessary.

[miu, 2016/11/16 22:30:06]

Done.

[miu, 2016/11/16 22:30:06]

Okay. There's already one in the content manifest, so we're good there. (I
wasn't sure if I needed one for the Chrome embedder as well; but I see from your
follow-up comment this should be removed.)
You could run pretty much *any* test in content_browsertests or layout_tests or
content_shell to expose this issue (before I disabled the logging yesterday).
FWICT, the log spamming started with your change:
https://codereview.chromium.org/2457493004 It only recently got back to me when
my manager asked me why I was spamming his test logs...

           "media_router::mojom::MediaRouter",
           "mojom::OmniboxPageHandler",
           "password_manager::mojom::CredentialManager",