Faulty reconnect to dmsg logic (also affects routes)

[0pcom]

The logic for reconnecting to dmsg is obviously faulty.

Many visors will establish a connection to dmsg but not maintain it indefinitely.

The exact nature of the issue is not apparent, also it's (apparently) only possible to check what dmsg server a particular dmsg client is using with another dmsg client

This is also apparently one reason why setup-node quits working, so addressing this issue should help to resolve routing issues

One thing we could do is start actually tracking dmsg clients with no delegated servers.