[lib] have edit entry message infos use e2ee op timestamp instead of …

…creationTime

Summary:
Addresses out of order edit and create robotexts. I introduced a bug by setting the message info timestamp to the `creationTime` instead of the time the edit op was created.

This results in out of order robotext for creating and editing entries. The fix is to use the op creation timestamp instead of `creationTime` which is when the entry was created.

Test Plan: Tested on iOS simulator. entries are back in order.

Reviewers: ashoat, tomek, marcin

Reviewed By: tomek

Differential Revision: https://phab.comm.dev/D13361

lib/shared/dm-ops/edit-entry-spec.js

@@ -15,14 +15,13 @@ import { dateFromString } from '../../utils/date-utils.js';
 import { rawMessageInfoFromMessageData } from '../message-utils.js';
 
 function createMessageDataFromDMOperation(dmOperation: DMEditEntryOperation) {
-  const { threadID, creatorID, creationTime, entryID, entryDate, text } =
-    dmOperation;
+  const { threadID, creatorID, time, entryID, entryDate, text } = dmOperation;
   return {
     type: messageTypes.EDIT_ENTRY,
     threadID,
     creatorID,
     entryID,
-    time: creationTime,
+    time,
     date: entryDate,
     text,
   };