The tally summary listener logic is in here.

This listener requires a chain transaction so when we handle a message, we insert the remittance entities and send the usages to the output topic in a single transaction.

However, Quarkus does not support chain transactions (see more in SWATCH-2545). Therefore, we're going to sligthly modify the listener from:

1. listen message from topic A
2. update database
3. send message to another topic B

To:

1. listen message from topic A
2. Is database updated? We need to check whether there is an existing remittance by tally ID already.
3. No, then update database
4. send message to another topic B