When creating nested curOps for update and delete we currently set their networkop field to be dbUpdate and dbDelete respectively, even though the operations came in as commands (dbMsg). This is inconsistent with the networkop setting on other operations and has potential for confusion.

Proposal: when creating nested curOp inherit the network op from the parent, use logicalop for logging if required to know the specific operation.