When updating replica set hosts in the shard registry, we only increment the counter of _rsmIncrement when the shard is not a config shard. This can prevent the ShardRegistry from refreshing to have the latest shards correctly.

This might have only become an issue after we introduced config shard in 8.0. Before that, the ShardRegistry was always constructed with a config server connection string, so it was not necessary to handle the case of config server.