[network] Delay peer outbound connection in ProtocolController if the dial failed

[dmitry-markin]

Currently, if the dial fails but the peer has high reputation, it's picked up as outbound connection candidate again, and dial is repeated on the next slot allocation (within a second). It would be nice to not dial such peers immediately.

Not super critical, but something to look into someday.

[altonen]

We need some additional considerations for this whole behavior.

If the dial fails, the address is considered undialable without any further testing. We should allow something like three failed dial attempts before the address is considered not working and can be removed. These dial attempts should not happen back to back because the node may be temporarily unavailable and later reachable again from the same address.

Right now the addresses are removed after one failed dial attempt which means some of the peers in PeerStore have no known addresses but they're still selected for an outbound connections. The dial will of course fail for these nodes but ProtocolController is not informed about this absence of known addresses which is a problem. DiscoveryBehavior should have the ability to remove known peers from PeerStore if it detects there are no available addresses for the peer.