Unify terminology somewhat.

The class extends the QDDebugService class, _not_ QDDebugServer. It's
right that there is also a QDEngineDebugServer being actually a service
in QtDeclarative, but we should probably fix this one too.

There is now a hook in QDeclarative itself for that.
Needs commit af2b28f9ca07057 of Qt

Previously, the user had to navigate to the context of a qml item in
order to edit its source code in Live Preview mode. This change tells
the client to update when new objects are created on server-side, and
makes the editing possible without having to manually trigger updates.

This one should be called when a component is changed and components
using it need to be reloaded.

The crumble path shows the current context of the debugger/inspector.

To show the object string id's, the debug protocol is used to get them.
The problem is that the required methods in QDeclarativeContext(Data)
are not exposed, and it's too late to do it for 4.7.0. Hence this change
should be reverted in 4.8 when more efficient way of getting the id's
comes available.

Also used 'int' instead of QDeclarativeDebugObjectReference for
the debug id in order not to use the private API from QMLJS

When the document is reloaded by the server, we need to refresh
refresh what was the loaded document, and refresh the debugIds

 * Windows does not like "QObject */* name */", warning about end
   of comment when rtunning into */*.