Pull consumer can hang in receive if RedeliveryPolicy is configured with max redeliveries

For a pull consumer (prefetch = 0) with a redelivery policy that enforces maximum redeliveries we now eagerly poison the incoming messages if they exceed the maximum redelivery value. The consumer does not attempt to issue another pull request in this case which can stall receive().

Also the consumer does not recompute the timeout if one is set leading to a longer wait than might otherwise be expected.