Add service to enable RPC style semantics over an event exchange about newton HOT 2 OPEN

It was very usefull to generate at each invoke some transactionalId, then put it to header + put to redis cache for example. and if remote consumer (ie http client) was timeouted. transactionalId removed from cache. When remote rpc will consumed, check transactionalId existence in redis. if it not exist - future work doesnt needed and we must throw an exception for recursive rollback upsteaming consumers. i think it could good for some of kind distributed transactions.

from newton.

Thanks @zotona

We're sending events over the muon event api (here -> https://github.com/muoncore/stack-event). We could back that using redis, but there's no implementation of that right now.

I think what we'll do is to have a service that emits an event as the request, then wait for a "fail" or "success" event using one of the subscribers as at https://github.com/muoncore/newton/blob/master/java/newton-sample/src/main/java/io/muoncore/newton/todo/TaskViewStore.java

from newton.