As part of PM-1645 we need to make sure that all usages of getCollectionDescription handles StaleShardVersion errors correctly. To make progress easy to follow, we renamed the old implementation getCollectionDescription_DEPRECATED and we're progressively changing it to the new implementation that throws if no collection metadata has been loaded.

In the case of rename collection, besides changing to the new implementation we have to ensure that:

• The calls to isSharded are performed only on the primary if we're applying a log operation
• The Collection Sharding State of temporary collections is not being check, considering temporary from the application's perspective
• All the calls to the rename collection command are passing through a router if the server has been started with the --shardsvr parameter and was added to a cluster