Provide option for max retires, and a call back when reached (potential DLQ)

Atm, user has to implement the max retry functionality themselves, as documented here: [retries docs branch](https://github.com/confluentinc/parallel-consumer/tree/retry-docs#retries)

This should be part of the system, as an option for a max retry count. When the count is reached, a callback should be executed, providing the user the WorkContainer and the chance to do something with it - maybe produce it do a different topic (DLQ) or simply log it.

Start with the retries documentation branch linked in the issue and trace the existing user-implemented retry flow around WorkContainer. Define how the max retry option and callback should interact, including the information passed when the limit is reached and how a caller could handle a DLQ or logging action. Done means the behavior and callback contract are implemented and covered by tests.

Written by the indexing model from the issue text.