MongoDB 6.0 is EOL in July 2025 #106
Description
We need to upgrade to the 6.x driver.
Some notes about new write concern defaults:
https://www.mongodb.com/docs/manual/reference/write-concern/#write-concern-specification
https://www.mongodb.com/docs/manual/reference/write-concern/#std-label-wc-default-behavior
https://www.mongodb.com/docs/manual/reference/command/setDefaultRWConcern/#mongodb-dbcommand-dbcmd.setDefaultRWConcern
https://www.mongodb.com/docs/manual/reference/write-concern/#standalone
In short, the default RW concern should be set by an administrator that sets up a cluster. The standalone version cannot be configured in this way, however. Therefore, the default config in the module should also set it properly so that standalone use also always works properly.
These options should always be set to true in deployments and in the default config for proper/safest application behavior: w: majority, j: true. This means we should not remove these options when upgrading to the v6 driver. Hopefully this all works out w/o there needing to be a difference between standalone vs. replicaset/shard setups where in the latter we might have to clear the write concern options in a deployment to allow it to use the proper defaults.