Node startup can enter a restart loop when L1 RPC endpoint is unreachable (no clear fatal error)

[porches-mopeds]

When the configured L1 RPC endpoint is unreachable or misconfigured, the Base node Docker setup can get stuck in a restart loop or appear to be “running” without making progress, while logs do not clearly point to the L1 RPC connectivity as the root cause. This makes the problem hard to diagnose for operators.

Steps to reproduce:

1. Go to your Base node deployment (Docker / docker-compose setup).
2. Configure the node to use an invalid L1 RPC endpoint (e.g., wrong URL or blocked network access).
3. Start the node using the standard startup command.
4. Watch container logs and/or container status for a few minutes.
5. See the node fail to make progress and/or repeatedly restart without a clear fatal message explaining the L1 RPC connectivity issue.

Expected behavior:
If the L1 RPC endpoint is unreachable, the node should fail fast with a clear, actionable error message indicating that the L1 RPC is required and cannot be reached. The failure should be explicit (non-zero exit) and should not present as a healthy-running node.