fix(schema): avoid applying default write concern to operations that are in a transaction

[vkarpov15]

Fix #11382

Summary

You aren't supposed to set write concern on operations in a transaction, rather set writeConcern on the transaction as a whole:

This PR makes it so that Mongoose doesn't apply schema-level write concern to operations that are within a transaction

Examples

[hasezoey]

Looks good, should the same be done for read-concern?

Transactions and Available Read Concerns

For multi-document transactions, you set the read concern at the transaction level, not at the individual operation level. The operations in the transaction will use the transaction-level read concern. Any read concern set at the collection and database level is ignored inside the transaction. If the transaction-level read concern is explicitly specified, the client level read concern is also ignored inside the transaction.

Do not explicitly set the read concern for the individual operations. To set the read concern for transactions, see Read Concern/Write Concern/Read Preference.

source

[vkarpov15]

We don't have support for schema-level read concern option, so this is a non-issue for read concerns currently.