Adjust with latest changes in RWebWindow

Avoid direct usage of RWebWindowsManager

By default all binary buffers for shapes created on the server,
but JSROOT able to create same data from TGeoShape. 

Binary size of cylindrical shapes can be large.
Provide a feature (not yet enabled) to transport TGeoShape to client and
build 3D object there. Let investigate performance and drawbacks

It is packed inside JSON - as compressed array.

It will contain different information on the node
Idea to avoid context menu as was used before but react on the click
events in the TreeTable

Instead specialized parsing of different request arguments
pack them together in one class. 
Should be possible to extend in the future

Only activated when gDebug > 0

Data model is slightly changed

Useful when dumped data can be analyzed with normal text viewer.

delivered

required

String path is more flexible (but more slow) way to address items in the
hierarchical structures. Now communication with browser component will
be redone with strings

For geometry viewer one do not need Component.js, central view can be
used as is

Now it always single node, but many elements can be assigned to the
top-level. To simplify handling, "invisible" top-level element is
introduced. It always there and corresponds to "/" address

Let use RBrowserItem as is on the client

Prepare for support of full model.
Server should be able to send full description to avoid many simple
transacations

Try to move browsing functionality to server.
Only required part is transformed to the client.
Allows to browse huge lists without big overhead for server/client
communication

ScanVisibles renamed to ScanNodes and has arguments - all nodes or only
visible to scan

Now when any volume highlighted in the geometry, 
special request send to the server with stack address.
Server tries to find ids for that stack and sends command for the
browser

When hovering with mouse over items in hierarchy, send hovered path to
the server, which can recognize exactly which element should be
highlighted. Idea to decouple as much as possible browsing of nodes
elements and drawing of geometry.

Highlight process should be shifted to the server.
It has to analyze which exact path was selected and send command to
client for highlight. If necessary, including extra rendering info

Now server manages search hierarchy, 
therefore it also responsible to clear it and inform client
Simplify communication pattern - no any shortcuts for query clearing

When submitting any selection/search query to server, 
hierarchy produced already on the server side and transmitted to client
Client should be able now show such hierarchy and switch back when
required to default one. 
This is next step to fully decouple hierarchy browser and 3D display.

Up to now drawing attributes as colors were delivered only when geometry
drawing was performed. Now it is collected immediately.

hierarchy includes just list of nodes with names and childs ids.
drawing data has all necessary information for drawing.
Now both can be used fully independently
Intention is to provide later alternative implementation for hierarchy
browsing

Now all necessary information for drawing send as single message (plus
raw data afterwards). Client first create ui5 layout and only then loads
JSROOT/EVE7 TGeo funcitonality. This speed-up appearance significantly.