net: inconsistent messages from logs vs CLI

[torkelrogstad]

When trying to connect to a new peer using the CLI after previously doing so, I get this error message:

❮ cargo run --bin thunder_app_cli -- connect-peer 172.105.148.135:6009
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.51s
     Running `target/debug/thunder_app_cli connect-peer '172.105.148.135:6009'`
Error: ErrorObject { code: ServerError(-1), message: "net error: already connected to peer at 172.105.148.135:6009", data: None }

Caused by:
    ErrorObject { code: ServerError(-1), message: "net error: already connected to peer at 172.105.148.135:6009", data: None }

However when looking at the server logs, it seems like the peer disconnected:

2025-01-20T14:28:51.594928Z ERROR thunder::node::net_task:779: Peer connection error addr=172.105.148.135:4009 err="connection error: timed out"
2025-01-20T14:28:51.595290Z  INFO thunder::net:132: Disconnected from peer at 172.105.148.135:4009
2025-01-20T14:28:51.595375Z  WARN thunder::node::net_task:771: Connection to peer closed addr=172.105.148.135:4009
2025-01-20T14:29:32.586625Z ERROR thunder::node::net_task:779: Peer connection error addr=172.105.148.135:6009 err="connection error: timed out"
2025-01-20T14:29:32.586883Z  INFO thunder::net:132: Disconnected from peer at 172.105.148.135:6009
2025-01-20T14:29:32.586936Z  WARN thunder::node::net_task:771: Connection to peer closed addr=172.105.148.135:6009