Add enterprise policy to turn off Bluetooth.

chrome/browser/chrome_content_browser_client.h

Index: chrome/browser/chrome_content_browser_client.h
diff --git a/chrome/browser/chrome_content_browser_client.h b/chrome/browser/chrome_content_browser_client.h
index f9693056ed12fd1c67941745545db98f23553d35..ee11a5b77d70694a53246c5ece4d87fbe281e1af 100644
--- a/chrome/browser/chrome_content_browser_client.h
+++ b/chrome/browser/chrome_content_browser_client.h
@@ -172,6 +172,7 @@ class ChromeContentBrowserClient : public content::ContentBrowserClient {
 #endif  // defined(ENABLE_WEBRTC)
 
   bool AllowKeygen(const GURL& url, content::ResourceContext* context) override;
+  bool AllowWebBluetooth() override;

[bartfab (slow), 2016/02/25 17:37:50]

We have a number of policies that control content settings. Can the Bluetooth
policy not be implemented the way those other policies are?

[Jeffrey Yasskin, 2016/02/25 20:38:50]

As discussed over IM, most of the policies are either chrome-only or go through
the PermissionManager tunnel through the Content API, which Mounir suggested I
not use for this. I'm imitating DefaultKeygenSetting for this one.

 
   net::URLRequestContext* OverrideRequestContextForURL(
       const GURL& url,