Setup node becomes unavailable because of inexistant sessions

[jdknives]

Describe the bug
The setup node has recently received an update to its logic to always dial to all available servers to improve its availability. It logs that it is corrected successfully to the servers on test deployment, but clients cannot dial to it for route establishment because the server does not have the setup node session registered.

[2022-07-26T12:21:39Z] INFO [dmsg_srv]: Stopped stream. error="dmsg error 307 - request cannot be forwarded because the next session is non-existent" session=02aa6fc7009d31622705cb3f2feaa8fe0da10c2ae081cf52e7ba7672bf097defad yamux_id=3

Meanwhile the setup node reports it is running well and connected.

[2022-07-26T12:33:58Z] DEBUG [dmsg_client]: Discovering dmsg servers...
[2022-07-26T12:33:58Z] DEBUG [dmsg_client]: Session already exists... remote_pk=024716428e6315d954356e9ad72bea32bb2b41aab5a54a9b5cb4313964016e64d8
[2022-07-26T12:33:58Z] DEBUG [dmsg_client]: Session already exists... remote_pk=03f6b0a20be8fe0fd2fd0bd850507cfb10d0eaa37dce5c174654d07db5749a41bf
[2022-07-26T12:33:58Z] DEBUG [dmsg_client]: Session already exists... remote_pk=02ae49c901480b49f9c40f6f90fa8e775cf9b00b61ded673a9b0776dfb7cccd374
[2022-07-26T12:33:58Z] DEBUG [dmsg_client]: Session already exists... remote_pk=02c5c21778c510f9bd29a54565db1ab20b9248804dce3d3fed171ae45a096f4037

Environment information:

• this happened on test deployment