Resending a message causes it to be resorted to the bottom

[Hocuri]

As of #8085, resending an old outgoing message causes it to be sorted to the bottom.

I'm wondering whether we should just revert #8085, in order to prevent adding more and more complexity.

Alternatively, we could add a flag is_resending to create_send_msg_jobs() that is checked before resorting. #7854 sets the msg.id to u32::MAX before resending in order to solve the same problem, but that seems hacky to me.

[link2xt]

I think reverting #8085 (and adding a test for the bug) is fine. The problem fixed by #8085 requires that clock jumps back and forth and does not happen during normal chatting.

[iequidoo]

Fixing the added code in a way like

        SELECT MAX(timestamp) FROM msgs WHERE
            -- From `InFresh` to `OutMdnRcvd` inclusive except `OutDraft`.
            state IN(10,13,16,18,20,24,26,28) AND
            hidden IN(0,1) AND
            chat_id=? AND
            id<=?5

should also help. Just reverting #8085 means that you won't be able to normally transfer a backup from a device having the clock a bit in the future.