writes_wait_for_write_concern has a set of commands with expected behavior around time-series views. In particular there are two commands (here, here) that are expected to fail with CommandNotSupportedOnView.

However, with viewless time-series collections this is no longer the case, since the time-series collection namespace will refer to the actual collection and not the view. So we do not expect these commands to fail with CommandNotSupportedOnView.

Also, this case is particularly interesting because it looks like if this applyOps command is issued and gets past the "CommandNotSupportedOnView" it will fail since the o2 field did not include an _id field.

Another interesting case is that we seem to expect it to pass when the collection is sharded here, but running the test on legacy time-series collections appears to skip this test case. On viewless time-series suites it is ran and fails.