…obal variables.

Introduced the JavaScript lo-dash utilities library on the way.
Fixed bugs and cleaned things up. Note that currently ONLY the
common partners code is working. Next up will be to bring back
the classic frequency-based sankey.

Idea: Data shouldn't go multiple times to the client. Also, filtering
often does not require contact to the server. So let the data JS
module cache data and let the client to filtering on its own.
For this, the widget layout now can switch off its default ajax
content loading. Then, the specific widgets have to take care of their
DOM elements and data loading on their own.
The data module now has methods to get data from the server, through
the index page. The idea is that all required data formats have a name
such as "relation counts" or "neighboursofnode" and such stuff.
This can then be cached within the browser.
The current issue is that the cache has to be emptied when a new
search is issued.

Separating the node order from the link weights.

…orrectly.

The reason was that the WidgetManager didn't create a new
Widget object if its internal map already knew a Widget by the given
name. But with the Ajax loading the map wouldn't be refreshed but
the HTML code would. So the elements manipulated by the old Widget
object did not exist any more and the newly added Widget object
was never created because the map already contained a Widget
for each widget name.