In causally_consistent_jscore_passthrough.yml, a section does not make sense since we don't inject any read/write concern in the suite. We should probably update the blacklist.
# Tests that won't work with an injected 'majority' readConcern # and/or an injected 'majority' writeConcern. Where a function is # listed the reason is we don't have a reliable solution to override # the write concern for that function.