When a collection stores data on shards other than the DBPrimary shard, it's necessary to send requests to all data-bearing shards to drop the collection's indexes locally. The standard dropIndexes command cannot be used for this purpose, as it does not support retryable writes, which is required to enable the Replay Protection mechanism described earlier.

Therefore, it will be necessary to create a new command to drop the collection's indexes locally on a shard supporting retryable writes.

The goal of this ticket is to:

• Implement the new command.
• Test on a sharding js test that the _shardsvrDropIndexesParticipant:
  • Actually drops all the collection's indexes of a shard.
  • The command is not executed if it's send with a stale txnNum.