The sharding subsystem ensures that the index backing a shard key (or the prefix of such an index) is non-multikey. This is make it clear which shard owns a particular document. There are some assumptions in the cascades rewrites that rely on this fact.

To avoid accidentally writing a unit test or translating a shard key in correctly, we should assert that the shard key provided to the optimizer metadata is non-multikey.