SERVER-62906 added a limitation to the number of characters in collection names for sharded collections. This seems to be an arbitrary limit, a long time ago, collection names were limited to 120 characters due to MMAPv1 in Windows, but this was removed by SERVER-41694, and it does not seems to be necessary anymore. Additionally, now that we'll be tracking unsharded collections, we should not have this limit. There are a couple of places where there is this restriction:

• In the coordinator, it is checked in two separate situations here and here
• In the sharding catalog manager

The purpose of this ticket is to first investigate the impact of removing this limit, and then removing it, achieving untracked collection parity in collection name limit.