More generic Storage querying. Query response mechanism put in place.
* Repository expects a Hazelcast queue to provide Query objects
* Its query drain picks up elements from this queue, evaluates them (performs queries on Storage)
* Results of the queries are put into a Hazelcast map (with ID of the query as key)

relates to #116
Merge branch 'master' of github.com:radek-macha/everBeen