Plumb invalidations from Tango to the extensions code for the Push Messaging API.

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.
 
 {
   "activeTab": {
     "channel": "dev",
     "extension_types": ["extension", "packaged_app"],
     "min_manifest_version": 2
   },
@@ skipping 210 matching lines @@
     "extension_types": ["extension", "packaged_app"]
   },
   "privacy": {
     "channel": "stable",
     "extension_types": ["extension", "packaged_app"]
   },
   "proxy": {
     "channel": "stable",
     "extension_types": ["extension", "packaged_app"]
   },
+  "pushMessaging": {
+    "channel": "dev",
+    "extension_types": ["platform_app"]

[Munjal (Google), 2012/08/14 18:56:37]

I think we should allow this feature for packaged apps, platform apps and
extensions.

[dcheng, 2012/08/14 21:39:59]

On #crx, I think Aaron mentioned that all the new permissions should be platform
app (he explicitly mentioned push messaging as one of those). I'm not sure what
the rationale was.

+  },
   // Note: runtime is not actually a permission, but some systems check these
   // values to verify restrictions.
   "runtime": {
     "channel": "stable",
     "extension_types": ["extension", "packaged_app", "platform_app"],
     "min_manifest_version": 2
   },
   "serial": {
     "channel": "dev",
     "extension_types": ["platform_app"]
@@ skipping 76 matching lines @@
   },
   "webRequest": {
     "channel": "stable",
     "extension_types": ["extension", "packaged_app"]
   },
   "webRequestBlocking": {
     "channel": "stable",
     "extension_types": ["extension", "packaged_app"]
   }
 }