Per jeff.yemin's comment in mongodb/specifications#563:

Can we add tests that assert both $out and $merge are treated as writes, e.g. by specifying a non-default write concern and including the write concern in the command started event?

The CRUD spec currently has no syntax for specifying database or collection-level options. While clientOptions were introduced in 5cf02a5 (SPEC-1210), they are not currently used in any tests and might not be supported a driver's spec test runner.

I propose we introduce the database and collection-level options, as exist in the transactions spec test format, and add these tests.