RevertSubmission tests use a hashmap and timestamps to generate the
results. The order is unspecified which the tests were not prepared for.
Inside Google the hashmap iteration order is randomized, and also inside
Google the tests are slower, which explains the reason why the tests
were flaky.
The solution involves sorting the results returned by RevertSubmission
by the numeric id of the change they are reverting (revert_of). Some
tests had to be adjusted accordingly.
UseClockStep annotations were removed since the tests are no longer
affected by timestamps.
Change-Id: I2472725776498fed663b8f4a19dbcff1c0188a32
64777c74be