Crash during rebalance when using configuration cache

This happens in a very specific case when:

1) The configuration cache is being used.
2) The client receives a NOT_MY_VBUCKET or similar which triggers a refresh of the config
3) The client tries to reload the configuration
4) The reloading fails
5) The client tries to grab the configuration from the network
6) The initial network grab fails as well
7) The network connection times out (i.e. via the lcb_connection-level timeout)

The timeout will be received, but there is an assertion inside the handler which checks that the instance is not already configured. The instance is not really configured, and the problem is that the config refresh code is callign the wrong function to refresh the configuration. It should be calling lcb_instance_connerr instead of lcb_connect