Improving error readability and handling returning infrastructure. #90
Description
When attempting to connect the wormhole-client with a cleared storage to the wormhole-server, which contains information about the peer, it returns an error:
time="2025-02-05T12:28:08Z" level=error msg="attempted peering from peer pp-bench-t-uks: error, public key mismatch"
wormhole-client hang with the following log:
time="2025-02-05T12:28:08Z" level=info msg="Log level set to info"
time="2025-02-05T12:28:08Z" level=info msg="Starting prometheus metrics server on 0.0.0.0:8090"
time="2025-02-05T12:28:08Z" level=info msg="No cached pairing response found, pairing with server"
The log should be more readable, indicating the existence of an existing peer configuration on the wormhole-server side.
How else can this issue be resolved without deleting the peers.db file?