Add SetImageData api to chrome.clipboard.

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 chrome/common/extensions/api/_features.md to understand this file, as
 // well as feature.h, simple_feature.h, and base_feature_provider.h.
 
 // If you add a new platform_app permission please update the "stubs_app" test:
@@ skipping 132 matching lines @@
       "96FF2FFA5C9173C76D47184B3E86D267B37781DE",  // http://crbug.com/642141
       "0136FCB13DB29FD5CD442F56E59E53B61F1DF96F"   // http://crbug.com/642141
     ]
   },
   "clipboardRead": {
     "channel": "stable",
     "extension_types": [
       "extension", "legacy_packaged_app", "hosted_app", "platform_app"
     ]
   },
+  "clipboardReadWrite": {

[Devlin, 2016/11/16 02:34:33]

Why do we need this permission?

[jennyz, 2016/12/07 01:21:48]

This permission is need to showing the warning string for "accessing clipboard
data" at the installation time of the app/extension who use chrome.clipboard.

[Devlin, 2016/12/09 15:23:43]

But we have clipboardRead and clipboardWrite; can't we just require both of
those instead of making a new permission?

[Devlin, 2016/12/16 02:05:08]

This still wasn't answered, either?

[Devlin, 2016/12/20 21:25:02]

Again, this doesn't seem to have been answered.

[jennyz, 2016/12/20 22:16:53]

Yes, that was what I originally did. But UI designer does not like it since it
shows two separate strings instead one on the installation warning dialog, which
violates one of the guideline in "CRX API Security Checklist"
(https://docs.google.com/document/u/1/d/1RamP4-HJ7GAJY3yv2ju2cK50K9GhOsydJN6KI...)
as follows:

Collapse multiple warnings into a single warning when possible.[2]
Example: Combine “Read files” and “Write files” into “Read and write files”.

The string is provided by our UI designer. Therefore, I added this combined
permission instead of requiring clipboardRead and clipboardWrite.

[Devlin, 2016/12/21 23:58:38]

We should be able to solve that using permission rules.

[jennyz, 2016/12/22 22:45:20]

Removed this permission and changed to add a permission rule to associate the
string with both clipboardRead and clipboardWrite permission.

+    "channel": "dev",
+    "extension_types": [
+      "extension", "legacy_packaged_app", "hosted_app", "platform_app"
+    ]
+  },  
   "clipboardWrite": {
     "channel": "stable",
     "extension_types": [
       "extension", "legacy_packaged_app", "hosted_app", "platform_app"
     ]
   },
   "cloudPrintPrivate": {
     "channel": "stable",
     "extension_types": ["extension", "legacy_packaged_app", "hosted_app"],
     // CloudPrint
@@ skipping 777 matching lines @@
     "channel": "stable",
     "extension_types": ["platform_app"],
     "platforms": ["chromeos"],
     "whitelist": [
       "A948368FC53BE437A55FEB414106E207925482F5",  // Files app
       "8C726564C6DBE7380BAB388DE6CC7EC93EB44B06",  // Video player
       "5065C83E84321221675D20FBE4DC43C655CC8C6F"   // Files app tests
     ]
   }
 }