fix(@mongodb-js/compass-schema-validation): Pass full namespace to updateCollection instead of passing collMod option

[gribnoysup]

Seems like this was an unintentional breaking change in data-service that resulted in compass-schema-validation not being able to update schema. The schema-validation plugin saveValidation method calls updateCollection like this, just providing a database name in namespace and passing collMod separately:

compass/packages/compass-schema-validation/src/modules/validation.js

Lines 473 to 480 in 81afb35

	dataService.updateCollection(
	namespace.database,
	{
	collMod: namespace.collection,
	validator: savedValidation.validator,
	validationAction: savedValidation.validationAction,
	validationLevel: savedValidation.validationLevel
	},

Before latest changes in data-service, the merge was happening in a way where collectionName derived from provided namespace was basically treated as a default value, not an override for whatever was provided in the options. This PR restores this behavior

[rose-m]

Oh nooooo - I'm sorry! And I thought I had eliminated all the places where I messed that order up :(

[addaleax]

Maybe leave a comment to prevent somebody from reverting this again? Because the "broken" code would definitely have been the one that would have looked more correct to me

[gribnoysup]

@addaleax yeah, fair point. Seems like this updateCommand call in schema-validation was the only one that wasn't passing the full namespace to the method, so I changed that and removed collMod from the passed flags. Saying that, I learned something new today! 😄 The order of keys in command passed to the server is important and because of that collMod needs to be the first property there. So I'm keeping the change in native-client, but I made flag types stricter and added a comment explaining what's going on. How does it look now?