Make `renameCollection` in a cluster pass through the config server

Currently, the rename collection command is being directly routed to just one shard, namely the db's primary shard since it just accounts for unsharded collections.

Aim of this ticket is just to add an additional hop (router -> config server -> primary shard). As part of PM-1965, DDL commands are expected to pass by the CSRS in order to choose which code path to follow based on the FVC status.