tests: adding sample message and a websocket client

- the client currently replays sample messages and gets expected results from chromium
- it will be used to ensure that debugium behaves the same
devtools: InspectorBackendDispatcher

- init 'can' messages handled and tested
- tests fail on 4th message which is not a 'can' message
devtools: adding Console handlers

- assuming we have no console agent these handlers return protocol errors
- also reorganized the code base a bit to have all dispatcher things in one dir
devtools: adding Network handlers

- we don't expect to have a network agent, therefore all these methods return protocol errors
devtools: Page handler and InspectorPageAgent

- Page.enable and Page.getResourceTree (without node core modules at
  this point)
frontend: adding devtools front-end based on 08e97a9

- node-inspector update scripts not fully working
- need to come up with update strategy, possibly using gyp
devtools: serving frontend assets

- implemented server up to upgrade
- only change to front-end devtools was adding devtools_discovery_page
devtools: implementing websocket

- hooked up to InspectorBackendDispatcher
- serves resource tree, but not resources themselves yet
- fixed resource tree bug (wasn't matching protocol properly)
devtools: implemented getResourceContent

- at this point all scripts and their content are shown in devtools
devtools: adding console and network agent

- at this point no more protocol errors are reported
- instead certain messages are ignored and an empty result sent back
- unimplemented methods are still logged as an error, but an empty
  result sent back nevertheless
- the effect can be seen when setting a breakpoint which gets removed
  immediately when the reply is an empty result
server: minor improvements
devtools: HeapProfiler that currently ignores all methods
devtools: Debugger that ignores all messages at this point
devtools: DebuggerAgent interface

- added RuntimeAgent and IndexedDBAgent with limited functionality in
  the process in order to avoid warnings
- fixed securityOrigin not sent for getResourceTree
- storing scripts by id

Still encountering the following problems

- we should see Debugger.getScriptSource after replying to
  Page.getResourceContent, but don't

Somehow when setting a breakpoint it is unable to find the breakpoint
target although it knows about the script and it's source (sends along
scriptID and got resourceContent of that ID before).

The backend sends back an ok with the info about the breakpoint set and
at this point the UI tries to add it but has trouble mapping it to a
UILocation.
As a result the breakpoint never gets set properly and we are also
unable to remove it.

Stacktrace:

```
Uncaught TypeError: Cannot read property '_rawLocationToUILocation' of null Main.js:formatted:22893
WebInspector.DebuggerWorkspaceBinding.rawLocationToUILocation Main.js:formatted:22893
WebInspector.BreakpointManager.TargetBreakpoint._addResolvedLocation Main.js:formatted:26244
WebInspector.BreakpointManager.TargetBreakpoint._didSetBreakpointInDebugger Main.js:formatted:26219
didSetBreakpoint Main.js:formatted:22445InspectorBackendClass.AgentPrototype.dispatchResponse Main.js:formatted:5262
InspectorBackendClass.Connection.dispatch Main.js:formatted:5071
InspectorBackendClass.WebSocketConnection._onMessage
```
cleanup: removing code duplication
debug: improved logging
frontend: adding unminified version of front-end

- when ./lib/server/main.js is launched with --dev flag those are used instead
- this eases debugging as the files are as authored originally, i.e. neither concatenated nor minified
docs: building chromium, generating front end and how to run things
frontend: turning on message logging in browser console for front-end-dev
frontend: adding module json files to front-end-dev