HRCPP-126 Segfault with cluster and connectionPool with minIdle > 0

https://issues.jboss.org/browse/HRCPP-126

Moved the responsability of issuing the startup ping from the TransportObjectFactory to the TcpTransportFactory.

This avoids issues related to TcpTransportFactory.servers being updated as a result of a new topology being received in the ping response while iterating over the entries in TcpTransportFactory.servers.

The initial cause of the segfault was: the servers.clear() call in updateServers calls the destructor of the InetSocketAddress passed as parameter to makeObject() but the object is used again before makeObject() returns.