Details
Description
On 5.0.2, it was made that the following commands are ran with a sessionId & txnNumber attached:
_shardsvrCreateCollectionParticipant
_shardsvrDropCollectionParticipant
_shardsvrRenameCollectionParticipant
_shardsvrRenameCollectionParticipantUnblock
However, 5.0.0 binaries did not attach it yet. So for backwards compatibility, those commands do not enforce that they are run as a "retryable write". After 6.0 branches out, we will be guaranteed that no more binaries that do not attach the sessionId are in the cluster. This ticket is to enforce that those commands are run with sessionId & txnNumber