Issue with updatedAt field showing incorrect values in document list

[blurfx]

What happened:

There is an issue with the updatedAt of a document showing another document updatedAt. Specifically, the updatedAt in the document list is being reversed and reflecting a different document's value.

This issue occurs during the bulk retrieval of document lists using this patch. In this process, there is no guarantee that the order of the keys passed to the DB query matches the order of the documents in the query result.

What you expected to happen:
The updatedAt field in the document list should accurately reflect the updatedAt of each respective document.

How to reproduce it (as minimally and precisely as possible):

1. Use the bulk retrieval method for document lists.
2. Update some document
3. Compare the updatedAt fields in the document list with the actual updatedAt values of the documents.

Anything else we need to know?:

I think this issue should be handled on the client side, because the query result(document list) from the server may not always contain all the documents of given keys.
For example, when document keys [1, 2, 3] are passed to the server and document 2 does not exist, result should be [1, 3].

Environment:

• Operating system:
• Browser and version:
• CodePair version:
• Yorkie version: v0.4.28

[blurfx]

cc @raararaara

[raararaara]

To solve this issue, how about converting the result of yorkieDocumentList into [id, yorkieDocument] format and mapping it?

codepair/backend/src/workspace-documents/workspace-documents.service.ts

Lines 82 to 84 in fd62043

	const yorkieDocumentList = await this.findManyFromYorkie(
	slicedDocumentList.map((doc) => doc.yorkieDocumentId)
	);

cc @blurfx