fix rpc responses processing by block for bad replies

This fixes a bug where the rpc client stops processing incoming rpc responses
with the user specified block when encoutering the reply of a broken or
misconfigured node.

Currently if one node in the collective responds with statuscode 2,3,4 or 5 the roc client raises an exception in `process_results_with_block` and all pending responses from other nodes are lost when calling an action and supplying a block for processing the responses as the come in.

I don't see why replies from misconfigured nodes (e.g. outdated agents) would be treated any other then failed replies from working nodes (status 1).