Add tests for CWS restriction of Nacl plugin invocation.

chrome/test/data/extensions/native_client/manifest.json

Index: chrome/test/data/extensions/native_client/manifest.json
===================================================================
--- chrome/test/data/extensions/native_client/manifest.json	(revision 0)
+++ chrome/test/data/extensions/native_client/manifest.json	(revision 0)
@@ -0,0 +1,11 @@
+{
+  "key": "MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCp40PYAXfSDlzCW1f5MDzRW64h0YhgV7MX8Frem0vO1ZAlq/mlUO4KxwkF2AZliFScO4Cc3CYpO6jpHXwz27tUwaN46C/LzYO7u/kb2piOep8gClvZ64EMnDv5PIoIeZlOJhkpnfs/5FbQt5sqT9avXX7YfLCLBJBql0U/V5615wIDAQAB",

[bbudge, 2011/08/05 18:40:10]

I copied this key from the only other 'component' extension test I could find.
Is there a better way to generate the key?

files/extensions/api_test/chrome_auth_private

[asargent_no_longer_on_chrome, 2011/08/05 22:39:46]

You should manually install your native_client.crx file, go open the Preferences
file in your profile directory and find the corresponding key entry for the
extension, and put that here.

The reason you sometimes have a key in the manifest and sometimes don't is a bit
complicated and was probably a design mistake, but I can explain in person why
it's that way if you are interested. :)

+  "name": "NaClExtensionTest",
+  "version": "0.1",
+  "description": "Tests Chrome Webstore restriction for Native Client.",
+  "permissions": ["nativeclient"],
+  "nacl_modules": [{
+    "path": "dummy.nmf",
+    "mime_type": "application/pdf" 
+  }]
+}