Provide mechanism to maintain order of related events during retries.

[stefan-cardnell-rh]

The non-blocking retry functionality does not maintain the order of related events. If an event A is in the retry flow and related event B comes in to the main consumer, this event should also be moved to the retry flow instead of processed.

We need to maintain in a store a list of retrying events based on their IDs.

Sources for implementation:

1. https://www.confluent.io/blog/error-handling-patterns-in-kafka/#pattern-4
2. https://medium.com/altitudehq/kafka-retries-and-maintain-order-of-retry-events-313482044351 - see "Maintain order of retry events"
3. https://www.youtube.com/watch?v=FO2ptQNQKhM&ab_channel=DanielTammadge

(Optional) Add blocking retry functionality as a non-complex way of providing ordered retries.