Comment 3 for bug 1882247

The two copies was due to lack of ordering of the tests, first testing three replicas, then testing two replicas. I've added ordering to the test updates now to run 2 replicas, then three so we can troubleshoot better if this happens again. I'm also adding in a check that the swift-storage units in the second region have settled with the updated replica count before writing the object. It is possible the condition was causing the written object to land on one of the region2 servers, then being replicated back off due to not yet having adopted the replicas=3 ring.