0.6.0

• Fix: the responseListener core component waited for queries not forwarded to workers, effectively creating a memleak
• Publishing messages is now done using the publish route from the write controller, instead of using a persist flag in the create route
• create, createOrUpdate and delete requests now notify subscribed users as-if the requests itself was a realtime message
• additional arguments can be provided in the subscribe.on request, allowing to filter notifications depending on their state, scope, or if this is a user event
• kuzzle rooms are now multi-channel, each channel corresponding to a subscription configuration. A user can subscribe multiple times on the same room using different channels
• subscribers now have to listen to the channel tag provided in the subscribe.on response, instead of the roomId. The channel tag is only that: the channel on which the user needs to listen in order to receive notifications