[repo] Add a publish/subscribe mechanism for inter-instance communication using zmq
Each repo can have a publishing and any number of subscribing sockets
whose addresses are specified in the instance's configuration. An
application or cube can subscribe to some 'topics', and give a callback
that gets called when a message matching that topic is received.
As a proof of concept, this introduces a hook to clean up the caches
associated with the repository when an entity is deleted.
A subscription is added using Repository::zmq::add_subscription;
the callback receives a list representing the received multi-part
message as argument (the first element of the message is its topic).
<table class="attributeForm" style="width:100%;"
tal:attributes="id tab_id | nothing;
class tab_class | nothing;">
<tr tal:iter="widget lines">
<th class="labelCol" tal:content="structure python:widget.render_label(entity)">attrname</th>
<td tal:define="error python:widget.render_error(entity)" style="width:100%;"
tal:attributes="class python:error and 'error' or nothing">
<div tal:replace="structure error">error message if any</div>
<div tal:replace="structure python:widget.edit_render(entity)" >widget (input, textarea, etc.)</div>
<div tal:replace="structure python:widget.render_help(entity)">format help if any</div>
</td>
</tr>
</table>