Upgrade to the newest three.js, updates for geometry viewer
This is preliminary 5.7.0 release

delivered

Such model used only there, other widgets do not need this model.
Allows to use browser in different places more easy

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

Main point - creation of specialized Model and ListBiniding for brwoser.
It is very unpracticale to use them with Component.js - making code not
modular

When browser obtains full hierarchy description, no extra requests are
required. But also one should not delete existing elements as partial
browser is doing 

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

This is special ui5 component, which allows partially to load browsed
items. Very very very sophisticated

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.

It is container for all data which are required to draw geometry or its
part. Idea to add nodes description itself to be fully independent from
previous transfers.

A different painting technique is now implemented for this case.

to avoid confusion and to allow to instantiate the templates of
both free functions and use them in fully compiled DFs.

This patch removes the redundant norm context method arguments.