SERVER-104220 Router must take into account drop collection write concern error (#35328)

GitOrigin-RevId: 9373888b96d38f782019d397d0eb415f443564c6

Author: pierlauro

jstests/concurrency/fsm_workloads/ddl/random_ddl/random_ddl_operations.js

@@ -56,7 +56,7 @@ export const $config = (function() {
 
             jsTestLog('Executing drop state: ' + coll.getFullName());
 
-            assert.eq(coll.drop(), true);
+            assert.commandWorkedIgnoringWriteConcernErrors(db.runCommand({drop: coll.getName()}));
         },
         rename: function(db, collName, connCache) {
             db = this.getRandomDb(db);

src/mongo/s/commands/cluster_drop_collection_cmd.cpp

@@ -139,7 +139,9 @@ class DropCmd : public DropCmdVersion1Gen<DropCmd> {
                 BSONObjBuilder result;
                 CommandHelpers::filterCommandReplyForPassthrough(remoteResponse.data, &result);
                 auto resultObj = result.obj();
-                uassertStatusOK(getStatusFromCommandResult(resultObj));
+                // TODO SERVER-103506 consider removing the following line since `writeConcernError`
+                // will be included in the DropReply (check SERVER-104220 for additional details)
+                uassertStatusOK(getStatusFromWriteCommandReply(resultObj));
                 // Ensure our reply conforms to the IDL-defined reply structure.
                 return DropReply::parse(IDLParserContext{"drop"}, resultObj);
             } catch (const ExceptionFor<ErrorCodes::NamespaceNotFound>&) {