The new unique index format needs to avoid doing an insert/remove pair of operations on the unique index table when in dupsAllowed mode - since applyOps shares a set of work across multiple threads unique index constraints can be temporarily violated. The violation will be resolved at each batch completion boundary.

We will be able to identify places in the code that require updates by looking for code that handles the dupsAllowed flag.

We should use the test case developed in SERVER-32502 to verify that the code is correct.