ClusterStore: fixed incorrect usage of strong-mq

Fixed ClusterStore.publish to publish the message with an empty topic.
The channel name is already stored in the message sent.

This change fixes the problem where sending a message to a channel
"disconnect:{random-id}" crashed the application with assertion error,
because strong-mq does not allow ':' in topic names.
test: added more logging