More instrumentation (Camera/VO/Blockly Logging)

@kadst43 @BrettASwift 
The idea with blocklyStarted was to create one event the listener in the instrumentationManager could hang it's hat on for both modifications to a graph program (y=x) or execution of normal movement blocks. An event is fired (vwf_view.kernel.fireEvent( vwf_view.kernel.application(), "blocklyStarted" );) in both blocklyRun and blocklyContentChanged (currentBlocklyNodeID === blocklyGraphID) If this seems convoluted (which it does to me now explaining it) then I could create two listeners for those two events instead. I think the goal was to avoid capturing content changes for non-graph program modifications.