When upgrading from replica sets to sharded clusters, we will need to move the collection from the replica set's primary node to the config server as we add the first shard. 

We will follow a process similar to the generic cluster parameter procedure. Specifically, we will hook into the AddShardCoordinator on the config server. This will allow us to clone the collection locally on the config server before we finally drop the collection from the newly added shard.

For testing, we should:
1. Start with a replica set test
2. Add some settings via setQuerySettings
3. Validate that the representative query is present in $querySettings
4. Start a sharded cluster and add the previous replica set as a shard
5. Validate that the representative query is present in $querySettings.
6. Directly connect against the new shard, and verify that the config.queryShapeRepresentativeQueries collection does not exist.