Client sort of detects if the gateway peer is down

[davidkel]

If the gateway peer goes down and stays down then the client just loops with the message

{"component":"CLIENT","timestamp":"2021-12-24T11:25:05.608Z","stage":"STATS","message":"WARNING: Client/Network may have stalled, no new transactions are being evaluated or endorsed"}
{"component":"CLIENT","timestamp":"2021-12-24T11:25:10.608Z","stage":"STATS","message":"WARNING: Client/Network may have stalled, no new transactions are being evaluated or endorsed"}
{"component":"CLIENT","timestamp":"2021-12-24T11:25:15.610Z","stage":"STATS","message":"WARNING: Client/Network may have stalled, no new transactions are being evaluated or endorsed"}
{"component":"CLIENT","timestamp":"2021-12-24T11:25:20.610Z","stage":"STATS","message":"WARNING: Client/Network may have stalled, no new transactions are being evaluated or endorsed"}
{"component":"CLIENT","timestamp":"2021-12-24T11:25:25.616Z","stage":"STATS","message":"WARNING: Client/Network may have stalled, no new transactions are being evaluated or endorsed"}
{"component":"CLIENT","timestamp":"2021-12-24T11:25:30.616Z","stage":"STATS","message":"WARNING: Client/Network may have stalled, no new transactions are being evaluated or endorsed"}
{"component":"CLIENT","timestamp":"2021-12-24T11:25:35.617Z","stage":"STATS","message":"WARNING: Client/Network may have stalled, no new transactions are being evaluated or endorsed"}
{"component":"CLIENT","timestamp":"2021-12-24T11:25:40.621Z","stage":"STATS","message":"WARNING: Client/Network may have stalled, no new transactions are being evaluated or endorsed"}
{"component":"CLIENT","timestamp":"2021-12-24T11:25:45.626Z","stage":"STATS","message":"WARNING: Client/Network may have stalled, no new transactions are being evaluated or endorsed"}
{"component":"CLIENT","timestamp":"2021-12-24T11:25:50.626Z","stage":"STATS","message":"WARNING: Client/Network may have stalled, no new transactions are being evaluated or endorsed"}
{"component":"CLIENT","timestamp":"2021-12-24T11:25:55.628Z","stage":"STATS","message":"WARNING: Client/Network may have stalled, no new transactions are being evaluated or endorsed"}
{"component":"CLIENT","timestamp":"2021-12-24T11:26:00.628Z","stage":"STATS","message":"WARNING: Client/Network may have stalled, no new transactions are being evaluated or endorsed"}
request to terminate received, stopping......
{"component":"CLIENT","timestamp":"2021-12-24T11:26:05.629Z","stage":"STATS","message":"WARNING: Client/Network may have stalled, no new transactions are being evaluated or endorsed"}
{"component":"CLIENT","timestamp":"2021-12-24T11:26:10.630Z","stage":"STATS","message":"WARNING: Client/Network may have stalled, no new transactions are being evaluated or endorsed"}
{"component":"CLIENT","timestamp":"2021-12-24T11:26:15.631Z","stage":"STATS","message":"WARNING: Client/Network may have stalled, no new transactions are being evaluated or endorsed"}
{"component":"CLIENT","timestamp":"2021-12-24T11:26:16.976Z","stage":"FINAL-STATS","message":"Submit: good=200, bad=5. Evals: good=310, bad=10"}

I assume this is down to the waitForReady call we have and the reason it doesn't terminate straight away is because wait for a timeout most likely the wait for ready grpc timeout.

Issue being raised to capture this behaviour so it's documented and also a consideration as to whether it could be reported as an exit code