Currently, in case a user issues a command to shard a config collection, it happens the following:

• A coordinator gets instantiated.
• The validity of the namespace is checked.
• The coordinator eventually fails and get released.

Since it is not correct to instantiate DDL coordinator for config namespaces (other than config.sessions), the check should be moved directly on the router. Similarly to the way the rename collection command checks for invalid namespaces.