Sort revisions first by timestamp, then revision ID

We hit something like this as well, but I want to question the premise of the original report.

Why would a revision id that is higher than another revision have a timestamp that is earlier?

Since revision_id auto increments, there is no reason for this to be the case under normal operations.

This seems like a bug in the way migrations may be handled rather than something that needs to be addressed here.

Preferable change -- actually print the revision ID next to the timestamp. (This is part of 🐛 Inconsistent moderation state for translated content Needs work ) and could be applied here.

The last submitted patch, 15: 3276716-15-sort-by-revision-timestamp-8.x-1.1.patch, failed testing. View results →
- codesniffer_fixes.patch Interdiff of automated coding standards fixes only.

+1 on #17/18.