op-node: app should should retry establishing connection with l2 node untill it suceeds

[vladopajic]

When op-node is started it will halt process if connection with l2 could not be established.

Log example:

t=2023-08-14T09:31:26+0000 lvl=eror msg="Unable to create the rollup node"      error="Post \"http://eth-node-1:8545\": context deadline exceeded"
t=2023-08-14T09:31:26+0000 lvl=crit msg="Application failed"                    message="Post \"http://eth-node-1:8545\": context deadline exceeded"

Instead of halting processes it might be better if node keeps running and tries reconnecting with l2 node until it succeeds, and printing log messages with current status.

[tynes]

Def open to a PR implementing this

[protolambda]

Stale issue, closing this. The op-node by now does retry, and with backoff, and a maximum number of attempts.

[protolambda]

Correction: it does retry, but only for L1 connection, not L2.