Chat timestamps "leap" into the future on restart

[placer14]

Report from @drwasho:
Everything below is done using the mobile package:

1. I created a node with 13.3 (tag)
2. Sent a chat message to someone offline (don’t think it matters whether they’re online or offline)
3. Shutdown, fast forward to the latest master and startup, and I see [MigrateUp] [NOTICE] running migration 023 changing schema to version 024...
4. Legacy timestamp remains, no problems there
5. Send a second message, which has the new timestamp… still sorted correctly every
6. Shutdown the node and restart, and I see this again: [MigrateUp] [NOTICE] running migration 023 changing schema to version 024...
7. Now both timestamps are wildly incorrect (e.g. 2188-01-13T22:47:40.156157952+10:00)
8. Every time I run the node, I see [MigrateUp] [NOTICE] running migration 023 changing schema to version 024... and the timestamps change, getting crazier (edited)