Add schema chrome-extension-resource:// for extension resources

chrome/test/data/extensions/api_test/accessible_cer/manifest.json

Index: chrome/test/data/extensions/api_test/accessible_cer/manifest.json
diff --git a/chrome/test/data/extensions/api_test/accessible_cer/manifest.json b/chrome/test/data/extensions/api_test/accessible_cer/manifest.json
new file mode 100644
index 0000000000000000000000000000000000000000..6776691a96d1ed85df7ef60fbbc48dfcefb71063
--- /dev/null
+++ b/chrome/test/data/extensions/api_test/accessible_cer/manifest.json
@@ -0,0 +1,20 @@
+{
+  "name": "Access chrome-extension-resource:// test",
+  "version": "0.1",
+  "manifest_version": 2,

[Aaron Boodman, 2012/04/16 18:56:15]

We should make the default security policy for manifest_version=2 allow
chrome-resource://.

[Peng, 2012/04/17 13:52:05]

Done.

+  "description": "Access chrome-extension-resource:// test",
+  "platform_app": true,
+  "app": {
+    "launch": {
+      "container": "shell",
+      "local_path": "main.html",
+      "width": 100,
+      "height": 100
+    }
+  },
+  "permissions": [
+    "experimental",
+    "chrome-extension-resource://analytics"

[Aaron Boodman, 2012/04/16 18:54:36]

We don't need a permission for this. Also, perhaps it would be better to use
just chrome-resource for the scheme, to not couple it to extensions.

[Aaron Boodman, 2012/04/16 18:56:15]

Actually, I don't see this getting checked anywhere in the patch. Is it just old
test data that didn't get removed?

[Peng, 2012/04/17 13:52:05]

Done.

+  ],
+  "content_security_policy": "script-src 'self' chrome-extension-resource://analytics; object-src 'self'"
+}