Fix bug where base relation was all

By basing on all rather than available_for_review, notices already in
review got moved to your queue, incorrectly.

This also uncovered a Postgres behavior where using .uniq, .order, and
.update_all in one scope-chain lead to an error.

To get around this, I removed the .order scope when selecting notices
available for review.

We will eventually want control over the order in which notices
available for review are selected into the queue, but I'm pushing that
logic out until we implement priority which will likely be what we order
by.