Mongos can't use remoteCursors for bulkWrite like other cluster commands because it will need to consume write results from the shards first before determining what to do next as a router. Given this nature of a router, mongos needs to cache response for each individual WriteOp. And there is no memory limit for it today.

Similar to SERVER-76026, this ticket is to limit memory usage (e.g. capped at 100MB) for the WriteOp responses cached on mongos. And this will effectively also limit memory usage for each bulkWrite response cursor.

The end goal is to limit the memory usage when we build or cache responses for bulkWrite ops. Once this limit is hit, we should stop executing the remaining operations in this bulkWrite.