Devtools: [WIP] Implement enhanced devtools extension language APIs

Source/devtools/front_end/inspector.json

Index: Source/devtools/front_end/inspector.json
diff --git a/Source/devtools/front_end/inspector.json b/Source/devtools/front_end/inspector.json
index 57270ec424343b3775e7611ab84445fac317c12d..24b09bea6b09499c6add7939155fce6b52e4b994 100644
--- a/Source/devtools/front_end/inspector.json
+++ b/Source/devtools/front_end/inspector.json
@@ -1,6 +1,7 @@
 [
     { "name": "platform", "type": "autostart" },
     { "name": "main", "type": "autostart" },
+    { "name": "languages", "type": "autostart" },

[pfeldman, 2015/08/13 21:15:46]

This should not be autostart - extensions module would wake it up.

[wes, 2015/08/14 01:13:32]

If "components" or "extensions" module has a real dependency on it, doesn't that
mean it needs to be "autostart", too? Am I wrong? (I know the CC script throws a
fit if you claim an autostart module depends on a lazy one, so I don't think I
am?) Or are you proposing that everything it does should be behind lazy
interfaces and facades, and those modules should become dependent on those
interfaces, allowing it to be lazily loaded? 

[pfeldman, 2015/08/17 21:15:51]

If languages has API and compact implementation, it is bind for it to be
autostart (it would be very similar to bindings).

     { "name": "components", "type": "autostart" },
     { "name": "ui", "type": "autostart" },
     { "name": "sdk", "type": "autostart" },