Get node-inspector to work much better in the presence of proxies.

Get node-inspector to work in the presence of proxies.  Put proxy checks
in Runtime_GetLocalPropertyNames(), Runtime_GetLocalElementNames(),
Runtime_DebugGetProperty(), Runtime_DebugGetPrototype(), and return
"empty" answers rather than throwing "illegal access".  The result is
node-inspector seems to work fine -- you just can't expand the contents of
variables which are proxies.

You can even debug class code.  The easiest way we currently know to put a
breakpoint in class code is to put a 'debugger;' statement in the class code and
reload the class definition.  However, you can also step into class code or return
into it if it is on the stack.