SmashPig currently uses the same database table for 'permanently' damaged messages (ones that might need manual fixing) and messages that should be sent back to their original queue after a wait (ones that may depend on a message in another queue to process first).

There is a 'retry_date' column on the 'damaged' table which flags a message as waiting to be requeued and not for display in the damaged message browser.

We can afford a dedicated 'retry' table in the SmashPig db and separate class in the codebase.