Add --retry-count option

[ryanwitt]

This would control the number of failures allowed before the queue sends jobs to failed.

usage: --retry-count <number>

[ShaneOH]

@ryanwitt I would consider this as potentially redundant:

• Expected retries can be handled by application code (e.g. see 429 code => application code should re-enqueue onto original queue with --delay option)
• Any given failure will be sent to a _failed queue which should then have its own retry policy: https://github.com/suredone/suredone/issues/9553

So like you mentioned on the call, I'm not sure we need to spend time adding retries onto "normal" queues since that can be handled via app code + failed queues

[ryanwitt]

As per discussion with @ShaneOH, this makes more sense as a retry count on the failure queue, so this will be closed in favor of #24 which has a --dlq-after option which specifies the number of failures on the _failed queue before request will be driven to DLQ.