Retry faucet operations on benchmark

[ndr-ds]

Motivation

When running with a hundreds of wallets, we might be able to overwhelm the faucet, and some requests might fail. So we should retry.

Proposal

Retry

Test Plan

Will benchmark a network with this code

Release Plan

• Nothing to do / These changes follow the usual release cycle.

[ndr-ds]

• Add create network actions latency to dashboard #5008 : 2 dependent PRs (#5010 , #5013 )
• Measure operation/message execution latency in microseconds #5007
• Add create network actions latency metric #5006
• Forward cross chain messages for different recipients actually in parallel #5005
• Add cross chain queue wait time and chain worker request queue wait time #5000
• Add cross chain message tasks to dashboard #4999
• Track chain worker request queue wait time #4998
• Track queue time for cross chain messages #4997
• Add Operations per second and Incoming bundles per second to dashboard #4995
• Retry faucet operations on benchmark #4994 👈 (View in Graphite)
• Fix monitoring stack #4992
• Add bundle and operation counters #4991
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.