Queries against sharded collections fail after upgrade to CSRS due to caching of config server string in setShardVersion

setShardVersion caches the config server connection string, and errors if it receives a connection string different than what it expects. This means that if a shard primary is sharding aware with an SCCC setup, then the cluster is upgraded to using CSRS, any future sharding operations that need to run setShardVersion will fail due to the cached config server string not matching.