Check writeOptions against the latest insertOne, insertMany, and bulkwrite apis

[aljones15]

While we are updating the options we might want to compare our current writeOptions:

bedrock-mongodb/lib/config.js

Lines 55 to 60 in a598ac4

	config.mongodb.writeOptions = {
	j: true,
	w: 'majority',
	multi: true,
	forceServerObjectId: true,
	};

Against the places where they are used:

http://mongodb.github.io/node-mongodb-native/3.6/api/Collection.html#insertOne
http://mongodb.github.io/node-mongodb-native/3.6/api/Collection.html#insertMany
http://mongodb.github.io/node-mongodb-native/3.6/api/Collection.html#updateOne
http://mongodb.github.io/node-mongodb-native/3.6/api/Collection.html#updateMany
http://mongodb.github.io/node-mongodb-native/3.6/api/Collection.html#insertOne
http://mongodb.github.io/node-mongodb-native/3.6/api/Collection.html#bulkWrite

Still used:

• w
• j
• forceServerObjectId
• multi (this appears to have been deprecated in favor of insertOne vs insertMany)

[mattcollier]

@aljones15 I putting this here but it could also be put in another issue if that's better.

bedrock-mongodb/lib/config.js

Lines 56 to 58 in 022fd8b

	j: true,
	w: 'majority',
	multi: true,

But @dlongley and I were discussing this recently and the idea that w and j are being included in the writeOptions on a per API basis is probably something that we should discontinue.

@dlongley I note that the 3.x mongodb driver does still include these options: https://mongodb.github.io/node-mongodb-native/3.3/api/Collection.html#insertOne

Is the implication that options specified on an API call will override the client connection options?

[aljones15]

just so this is know in Mongo Driver 4 you can not mix writeConcern with explain on aggregate calls:

  error: MongoInvalidArgumentError: Option "explain" cannot be used on an aggregate call with writeConcern

So writeConcern must be removed at the top level in order to work with node mongo driver 4.

[dlongley]

Addressed by #107.