Investigate issue with the periodic network readiness waiting failures

[shimkiv]

More details: https://discord.com/channels/484437221055922177/1210110696746909706/1274266526211506260

[jmikedupont2]

The `Waiting for the blockchain network readiness...` might not really mean network is not ready. You can check it by `zk lightnet explorer` (to see if the network progresses with new blocks) or manually doing the same with `http://localhost:8080/graphql`.

> it got stuck
It will exit eventually after the calculated amount of attempts to check the network readiness.

If you see it "stuck" on waiting for more than some meaningful time (depends on resources available for the docker engine) and you see network indeed progresses then you can interrupt `zk lightnet start` with whatever signal (`ctrl+c` for example). It won't harm in any ways.
It also seems that `...stop` + `...start` solves the issue.

Meanwhile I'll investigate why it doesn't work as expected from time to time.````

[jmikedupont2]

I can see that it runs for 3x longer, so might be a wait or race condition. I will keep my eyes open.

[shimkiv]

Was not able to replicate the issue. Added more debug logging and let's keep an eye on it. To enable debug logging one can use the following envar:

DEBUG=* zk lightnet start