do a second majority write on oldPrimary before committed read in read_committed_after_rollback.js

The secondary can lose it's sync source after it replicates the new write, but before it gets the new committed optime here. Doing a second write should ensure that the new committed optime gets propagated.