Add Tracing.getCategories to protocol.json.

Source/devtools/protocol.json

 {
     "version": { "major": "1", "minor": "1" },
     "domains": [{
         "domain": "Inspector",
         "hidden": true,
         "types": [],
         "commands": [
             {
                 "name": "enable",
                 "description": "Enables inspector domain notifications."
@@ skipping 4108 matching lines @@
                 ],
                 "returns": [
                     { "name": "sessionId", "type": "string", "description": "A system-unique identifier of the tracing session that allows associating of some of the trace events with the inspected page" }
                 ],
                 "handlers": ["browser", "renderer", "frontend"]
             },
             {
                 "name": "end",
                 "description": "Stop trace events collection.",
                 "handlers": ["browser", "frontend"]
+            },
+            {
+                "name": "getCategories",
+                "description": "Gets supported tracing categories.",
+                "returns": [
+                    { "name": "categories", "type": "array", "description": "A list of supported tracing categories." }

[caseq, 2014/06/17 18:38:23]

You probably want items: { "type": "string" } here.

[chrishenry, 2014/06/17 18:53:41]

Curious, why should this be string instead of an array? The categories are
really a list of strings. I can of course send them as comma-separated string.

Here's the implementation:
https://codereview.chromium.org/339743004/

This isn't working yet, so far I'm getting undefined from ChromeShell. s:

+                ],
+                "handlers": ["browser", "frontend"]

[chrishenry, 2014/06/17 17:23:50]

I'm not sure about this handlers field. Do you know what this is for? What would
be the right value here? I just copied it from Tracing.end above.

[caseq, 2014/06/17 18:38:23]

This one is correct (this tells the code generator in what components the code
needs to be generated; here, the command will be sent from front-end to the
browser and will not be handled in the renderer, so you just want these two).

[chrishenry, 2014/06/17 18:53:41]

Thank you!

I'm curious why Tracing.start needs to be handled in the renderer, but
Tracing.end doesn't. What does it mean by handled by the renderer?

             }
         ],
         "events": [
             {
                 "name": "dataCollected",
                 "parameters": [
                     { "name": "value", "type": "array", "items": { "type": "object" } }
                 ],
                 "description": "Contains an bucket of collected trace events.",
                 "handlers": ["browser", "frontend"]
@@ skipping 54 matching lines @@
             {
                 "name": "dataAvailable",
                 "parameters": [
                     {"name": "value", "type": "array", "items": { "$ref": "PowerEvent" }, "description": "List of power events." }
                 ],
                 "handlers": ["browser", "frontend"]
             }
         ]
     }]
 }