Issue with Ledger Browser (UI) disconnecting from nodes

After running for an extended period of time the Ledger Browser (UI) can loose its connections to the nodes. Typically a restart fixes the issue. However it would be nice to find a more permanent solution.

This causes a few issues:
- The validator node status stops working. *The node status indicators (node circles) do not appear on the home page*.
- Under the covers the detailed node status is not collected, and since this is typically used to monitor the health of a `von-network` instance the ledger presents as non-functional (down).
- The DID registration controls stop functioning, since the connection to the ledger for writing transactions is lost.
- Ledger browsing functionality is lost, since connection to the ledger for reading is lost.
- From a client (agent) perspective the ledger typically continues to function without any issues, as it's only the Leger Browser's (`von-network` UI's) connection to the ledger that is affected.

No files or tests are named. Start by reproducing the Ledger Browser connection loss after extended runtime and trace how the UI collects node status and handles ledger read and write connections. Done means the browser remains connected and validator status, DID registration, and ledger browsing continue to work without requiring a restart.

Written by the indexing model from the issue text.