Sync remote events

The current remote events are async in the sense that the server fires them and there's no acknowledgement from the client that it's consumed them. Async enables reasonably performant remote events while handling server failures via the include current state options for when a failover is discovered.

Some applications however demand that the event is guaranteed to be fired before the cache operation has finished. Having to do remote sync events would be hurt performance considerably but there are situations when this is needed, e.g. the JCache TCK. The remote JCache implementation is including some logic to deal with this, but it might be better to implement this directly in the Hot Rod protocol in the future.