Add a new resmoke hook, which opens the change stream at the end of the test and checks general truths. This way, we are relying on the diversity of our tests to provide interesting sequences of commands issued to construct various edge case scenarios. This could potentially prevent bugs like SERVER-61026 from happening.

An example of an illegal sequence of events such a hook could potentially detect: “create (shard A), shardCollection (shard A), drop (shard A), create (shard A), insert (shard A), drop (shard B)”. Note how create and insert events from shard A happen before the drop event from shard B.