Move webstorePrivate DelegatedInstall functions into new dashboardPrivate API

chrome/common/extensions/api/_api_features.json

Index: chrome/common/extensions/api/_api_features.json
diff --git a/chrome/common/extensions/api/_api_features.json b/chrome/common/extensions/api/_api_features.json
index f3652dc4c5cad285411d25e073407f9b16515ae1..0a652bf09487c8658f3d60ab2719853d20a4ac02 100644
--- a/chrome/common/extensions/api/_api_features.json
+++ b/chrome/common/extensions/api/_api_features.json
@@ -246,6 +246,17 @@
     "dependencies": ["permission:cryptotokenPrivate"],
     "contexts": ["blessed_extension"]
   },
+  "dashboardPrivate": [{
+    "channel": "stable",
+    "contexts": ["blessed_web_page", "web_page"],
+    "matches": ["https://chrome.google.com/*"]
+  }, {
+    "channel": "stable",
+    "contexts": ["blessed_extension"],
+    "whitelist": [
+      "B44D08FD98F1523ED5837D78D0A606EA9D6206E5"  // Web Store

[not at google - send to devlin, 2015/07/31 14:42:20]

What does the webstore need from this?

[Marc Treib, 2015/07/31 15:28:42]

The webstore also needs to call this API - remote install is possible from both
the webstore and our dashboard. (That's basically the reason why this was in
webstorePrivate in the first place.)
Or was the question "why isn't the URL pattern above sufficient"? Because the
webstore is not in a web_page context, and if I add "blessed_extension" above,
then the API will be available to any extension.

Or alternatively, I might have misunderstood something, in which case please
correct me :)

+    ]
+  }],
   "dataReductionProxy": {
     "dependencies": ["permission:dataReductionProxy"],
     "contexts": ["blessed_extension"]