IMPORTANT: now you have to take extra care when your plugin makes a version jump (e.g. from SNAPSHOT to release or vice versa). Before building the new plugin you have to remove the old one from `bundle-deploy` manually. Only one version of a plugin must be deployed.

boolean isTopicInTopicmap(long topicmapId, long topicId)
->
Association getTopicMapcontext(long topicmapId, long topicId)
boolean isAssociationInTopicmap(long topicmapId, long assocId)
->
Association getAssocMapcontext(long topicmapId, long assocId)
Instead a boolean you get the "Topicmap Context" association, if exists.
To get the former semantics compare the return value `!= null`.
See dmx-plugins/dmx-tableview#9

Reverts 0c73cfaf
Geomap content works again
Change the topicmap -> content association again:
As role types "dmx.core.default" and "dmx.topicmaps.topicmap_content" are used,
the topicmap being at the "default" end.
Add 1 role type again:
"Topicmap Content"
dmx.topicmaps.topicmap_content

See nodejs-modules/dmx-cytoscape-renderer@240b3f8a
The 3 "reveal" actions (topic, assoc, related topic) expect a `noSelect` arg now (instead `select`) with inverted semantics. The arg is still optional. That is selection is the default. Arg must be specified only to suppress selection.