camel-hazelcast - Manage transactions with SEDA Consumer and improve the mapstore lifecycle

The transactions are not started when the seda consumer is used.

If the messages are stored in MapStore, seda consumer doesn't wait the end of transaction to remove data. It's a problem if the server crashes because data are lost.

The patch allows to resolve this problem because the message in mapstore will be removed only when the transaction will be finished.