handle network/server issues when forwarding a replay over http

we are retrying failing attempts to send messages only when handling the requests from the local queue, but not retrying when we handling the requests from the replay queue. this led to dropping some replies, especially when dealing with a lot of requests.

we should handle network/server issues when sending the replay over HTTP by retrying to send again in cases of

wasn't able to resolve twin DST (temporary issues accessing the explorer)
resolved but wasn't able to send the request due to TCP connection issues (we get this a lot, in most cases, it needed only another try to succeed)
send the request but received an error response from the remote RMB (with an exception for 4xx maybe)

threefoldtecharchive / rmb_archive

handle network/server issues when forwarding a replay over http #32