Delete the old hotwording integration.

chrome/common/extensions/api/_permission_features.json

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 // This features file defines permissions for extension APIs implemented
 // under src/chrome.
 // See extensions/common/features/* to understand this file, in particular
 // feature.h, simple_feature.h, and base_feature_provider.h.
 
 // To add a new whitelisted ID, SHA-1 it and force it to uppercase. In Bash:
@@ skipping 471 matching lines @@
     ]
   },
   "history": {
     "channel": "stable",
     "extension_types": ["extension", "legacy_packaged_app"]
   },
   "hotwordPrivate": {
     "channel": "stable",
     "extension_types": ["extension", "platform_app"],
     "whitelist": [
-      "8CE39F175D076AD6BDF7CBF418F2409558B367E3",  // hotword_helper
-      "09FDCB5851B8F3378DB630D06E316076E89C95A6",  // hotword nacl

[kcarattini, 2015/03/17 00:41:13]

Doesn't the 'new' hotword extension need to be listed here?

[Anand Mistry (off Chromium), 2015/03/17 03:00:46]

Done as a separate change since it's orthogonal to this one.

[kcarattini, 2015/03/17 22:55:21]

How was it working if it wasn't listed here in the first place?

       "B6356EFF4047BC5F868C7D91868B6F5C01951A8A"   // hotword_audio_verification
     ]
   },
   "identity": {
     "channel": "stable",
     "extension_types": ["extension", "platform_app"]
   },
   "identity.email": {
     "channel": "stable",
     "extension_types": ["extension", "platform_app"]
@@ skipping 460 matching lines @@
   },
   "webstorePrivate": {
     "channel": "stable",
     "extension_types": ["extension", "legacy_packaged_app", "hosted_app"],
     "whitelist": [
       "B44D08FD98F1523ED5837D78D0A606EA9D6206E5",  // Web Store
       "2653F6F6C39BC6EEBD36A09AFB92A19782FF7EB4"   // Enterprise Web Store
     ]
   }
 }