MV Register Map resolution is not deterministic
Add "8" || "9" concurrently into a MVRmap entry. One replica shows {"8, "9"}, the other shows {"9", "8"}. It shouldn't matter since the values are a set, but it should still not be that way: the content should not depend on the the order. This non-determinism may cause application-level bugs.