Unchained API: update blockbook websocket error handling

[kaladinlight]

Overview

Currently we attempt to reconnect to the blockbook websocket 5 times before failing and causing the pod to exit. This worked well for our self hosted infrastructure as an additional built in retry mechanism, but causes complete outages in the now nodes world if only websockets go down which we have seen.

References and additional details

websocat: WebSocketError: WebSocketError: Received unexpected status code (500 Internal Server Error)
websocat: error running

Acceptance Criteria

• api will no longer exit if blockbook websocket is down
• there will be a continued background retry loop to ensure websockets are auto reconnected once back

Need By Date

No response

Screenshots/Mockups

No response

Estimated effort

No response

[0xean]

done