Add new hotword extension for built-in hotword triggering.

chrome/browser/resources/hotword/manifest.json

+{
+  // Extension ID: nbpagnldghgfoolbancepceaanlmhfmd
+  "key": "MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDbHXRPiq2De9EJ+4pvNN6uE/D2avxrqyLSpA/Hq3II+btkPl1gboY3oUPTfevpVOFa90Y1c1b3/W682dXqybT0klIvFLKhdQx0LiVqSUQyIaDrwOCSo/ZcukbEwDRojegWymCjHvX6WZk4kKZzTJYzY1vrp0TWKLhttEMN9KFmowIDAQAB",
+
+  "name": "Hotword triggering",
+  "version": "0.0.1.0",
+  "manifest_version": 2,
+
+  "background": {
+    "scripts": ["manager.js"],
+    "persistent": false
+  },
+
+  "permissions": [
+    "*://*.google.com/*",
+    "chrome://newtab/",
+    "hotwordPrivate",
+    "tabs"
+  ],
+
+  "externally_connectable": {
+    "matches": [
+      "*://*.google.com/*",
+      "chrome://newtab/"
+    ]
+  },
+
+  "import": [
+    {
+      // TODO(amistry): For now, use a locally modified version of the external

[James Hawkins, 2014/08/08 09:20:18]

FWIW I don't think comments are supported in manifest.json.

[Anand Mistry (off Chromium), 2014/08/11 00:43:59]

In what way? Locally, I have working extension that builds on this change, and
it has no problems handling this comment.

+      // hotword extension. Replace with the ID of the new shared module
+      // containing the hotword detector.
+      "id": "bepbmhgboaologfdajaanbcjmnhjmhfn"
+    }
+  ],
+
+  "minimum_chrome_version": "38"
+}