Fix bad logic on standard Redis failed queue adapter
Fix bad logic on standard Redis failed queue adapter

There were some checks for the queue name in this adapter, in place to
provide a similar API to the multi-queue backend, but with assertions
that we were operating on the right queue.

Problem is: the logic was backwards! D'oh!

This centralizes the check in a method with the correct logic.

hoffmanc/resque,bonekost/resque,vladimirich/resque,lileeyao/resque,ktheory/resque,m0dd3r/resque,delectable/resque,igorjancic/resque,sufery/resque,jacknguyen/resque,ngpestelos/resque,l4u/resque,redhotpenguin/resque,bhighley/resque,lileeyao/resque,ducthanh/resque,delectable/resque,partap/resque,fmitech/resque,timo-p/resque,AlexVPopov/resque,lukeasrodgers/resque,ktheory/resque,paran0ids0ul/resque,fmitech/resque,ychaim/resque,m0dd3r/resque,igorjancic/resque,jonatas/resque,tylerdooling/resque,kangkot/resque,timo-p/resque,vladimirich/resque,sideci-sample/sideci-sample-resque,vietnt/resque,hoffmanc/resque,eileencodes/resque,ryan-drake-stoker/resque,stitchfix/resque,sufery/resque,l4u/resque,lukeasrodgers/resque,jacknguyen/resque,rutikasb/resque,sideci-sample/sideci-sample-resque,tylerdooling/resque,paran0ids0ul/resque,stitchfix/resque