ReplicatedHashMap does not correctly handle state transfer during a merge, leaving members with inconsistent map entries.

Specifically, on receipt of a MergeView no attempt is made to reconcile the state of all members. Each member retains the entries it had while partitioned, though all members will correctly apply subsequent mutations.

I've attached a unit test that demonstrates the bug and also a patch that corrects the behavior (specifically, by calling getState() on the coordinator of each subview on receipt of a MergeView).