Implemented activate/deactivate breakpoints.

* DebuggerAgent.setBreakpointsActive
Implemented 'Continue to Here' command

* DebuggerAgent.continueToLocation
Updated the Console methods under both Runtime and Debugger.

Method names: Runtime.evaluate, Debugger.evaluateOnCallFrame

To facilitate these, converters now exist for both Results/Values gotten from V8 via the debugger into Inspector Values and Error messages into Inspector Error objects.

Side Effect: Runtime.getProperties had to be updated to handle new types of values the Inspector is now slinging its way.
Breaking on an Exception now provides a reason.
Commands not used/supported, capability queries

Added no-op implementation for commands that are ignored by node-inspector,
e.g. CSS.enable.

Implemented (some of) capability queries called by front-end,
e.g. Worker.canInspectWorkers.

Implemented dummy Page.getResourceTree returning internal `node.js` as
toplevel frame. This file is marked as "main" in front-end source tree.

Removed the call to WebInspector._doLoadedDoneWithCapabilities()
from WebInspector.onWebSocketConnected, since it will be called
from Worker.canInspectWorkers response callback.

Also removed the call to WebInspector.showPanel() from
WebInspector.onWebSocketConnected, because panels are not created at that
time. (They are created by WebInspector._doLoadedDoneWithCapabilities(),
which will be called later.)
v8NameToInspectorUrl for `evaluate` scripts

Call to `evaluate` creates a new script with no URL.
This commit fixes v8NameToInspectorUrl so that it
returns empty string as URL in this case.
DebuggerAgent.getFunctionDetails()

Partial implementation of DebuggerAgent.getFunctionDetails(). There is no
easy way of obtaining scope-chain of the frame where the function was defined,
so we are returning an empty array for now.

Added unit-test verifying that v8RefToInspectorObject fills objectId
for functions.
Fixed DebuggerAgent.setPauseOnExceptions.

The previous version of setPauseOnExceptions did not work at all.

The current version always sends two `setexceptionbreak` requests,
one for `all` and another for `uncaught` exception type.
Code clean-up: removed unused code.

- Breakpoint class, breakpoint-related command handlers
- initial listing of breakpoints on front-end connect
- restoreSessionBreakpoints() (since front-end already restores all breakpoints
  on its own)
Removed test/hello.js

Removed hello.js which was presumably used for manual testing. We have
automated unit-tests in test folder now and hello.js did not play well
with mocha framework.