Should we merge iterum into Propono

[iHiD]

So the only thing now blocking me from releasing the pre-release of v2 is reading from failed queues. We seem to have once had code that to have code for this but it got refactored out at some stage. It's now hardcoded via iterum (which will stop working). Do we want to bake this into Propono core somehow.

@malcyL @ccare Thoughts pls.

[malcyL]

Iterum gave us something we could install and run either locally or on an server somewhere which provided rake tasks to easily replay messages. It's an operational tool outside of the application publishing/subscribing to those messages.

There is no reason why it couldn't be inside Propono itself. Keeping it inside Propono has the advantage that it is always kept up-to-date and working with the latest version.

Moving it inside Propono, would the user install the Propono gem globally, and then run a rake task?

[ccare]

We could possibly do something with a gem binstub, so adding propono to a project would give you a `bin/iterum` executable within the project.