Move socket API from experimental to dev channel and remove some dead code

chrome/test/data/extensions/api_test/socket/api/manifest.json

Index: chrome/test/data/extensions/api_test/socket/api/manifest.json
diff --git a/chrome/test/data/extensions/api_test/socket/api/manifest.json b/chrome/test/data/extensions/api_test/socket/api/manifest.json
index 4ca5cac8ce7ac9ec92f201dfbfb5b5f0bea07e1f..33702f5c1148279525038c5b6f2f99f788bb76ca 100644
--- a/chrome/test/data/extensions/api_test/socket/api/manifest.json
+++ b/chrome/test/data/extensions/api_test/socket/api/manifest.json
@@ -2,14 +2,13 @@
   "name": "chrome.socket",
   "version": "0.1",
   "manifest_version": 2,
-  "description": "end-to-end browser test for chrome.experimental.socket API",
+  "description": "end-to-end browser test for chrome.socket API",
   "app": {
     "background": {
       "scripts": ["background.js"]
     }
   },
   "permissions": [
-    "experimental",
     "socket"

[Peng, 2012/07/27 19:09:52]

I run browser test, no error happened. It because the old manifest file already
includes socket permission. 

[miket_OOO, 2012/07/27 19:21:24]

Great. Just for the sake of sanity, try removing the socket permission and
making sure that the test *does* fail. If not, then something's broken with the
permission framework. I'm slightly paranoid about this because it's the first
app API we've taken out of experimental, and I don't want anything to slip by
accidentally.

[Peng, 2012/07/27 19:31:42]

Done. Cases failed without socket permission.

   ]
 }