bug: reconnecting fails if the client was instantiated with server names without ports appended

[htbvo]

There is a bug in how server addresses are passed to the issue log on a connection error. Consider the case when the client is instantiated like so:

const client = new Memcached(['server-0.memcached.local', 'server-0.memcached.local'])

If the first attempt to connect to server-0 fails, then an issue is created for the address server-0.memcached.local:11211.
If the second attempt to connect to server-0 fails, then an issue is created for the address server-0.memcached.local.

The reconnects attempts for the second issue will never pass, since it's eventually going to call ping([server-0.memcached.local][1]) in connection.js.

All subsequent requests that get mapped to server-0 will see that it's unavailable, even if reconnect attempts spawned from first the connection issue for the first failure (server-0.memcached.local:11211) succeeded.