SERVER-139295ClosedFixed
Retry WriteConflict when acquiring/promoting/releasing the critical section
*Issue* During a DSC step down, DDLs can bubble up a WriteConflict error to the user (instead of the critical section code internally retrying it). *Analysis* [Acquiring, promoting or releasing the critical section writes via DBDirectClient with locks held|https://github.com/mongodb/mongo/blob/b2b94807a4d84159532979b97387cc806f691e0e/src/mongo/db/global_catalog/ddl/sharding_recovery_service.cpp#L282-L364]. In a DSC cluster, during stepdown we may hit a WriteConflict there due to