executeCommandAgainstDatabasePrimary is mainly used from cluster commands to execute ddl command against the primary such as here. However, the helper functions always attaches the ShardVersion::UNSHARDED. This is actually not needed. Once a shard enters in the Shard Role, it will validate the routing information and throw in case the nss is sharded, such as here

The UNSHARDED version should only be used when targetting specifically untracked unsharded collection. 

After SERVER-83399 a new helper called 

executeDDLCommandAgainstDatabasePrimary

 was introduced to only attach dbVersion

The goal of this ticket is to:

• Replace executeCommandAgainstDatabasePrimary with executeDDLCommandAgainstDatabasePrimary for coordinators command
• Evaluate whether to remove executeCommandAgainstDatabasePrimary if no longer needed. In case still needed, we could rename it to specifically express the intent of targetting untracked unsharded collection, and not just the primary.