fix: prevent truncating message timestamps when updating references to deleted quoted message

[MartinCupela]

CLA

• [ X ] I have signed the Stream CLA (required).
• [ X ] Code changes are tested

Description of the changes, What, Why and How?

When message.deleted event was delivered, the client code invoked channelState.removeQuotedMessageReferences(event.message);. This function was converting created_at, pinned_at, updated_at values of each quoting message to string using toString() method. That lead to truncation of milliseconds from each timestamp. Later the truncated timestamps distorted the decision logic in ChannelState._addToMessageList() in the following way,

1. the last message B in the list was also quoting another message A
2. the quoted message was deleted (timestamps of message B now truncated)
3. the message B was then updated and the WS event message.updated carried created_at timestamp with milliseconds
4. the message B in the state carried created_at timestamp without milliseconds
5. the updated B message was considered a new message but addIfDoesNotExist param for ChannelState._addToMessageList() is set to false when handling message.updated events
6. that leads to pure copying of the previous message list state without adding the updates

Solution is not to truncate the message timestamps, when updating references to deleted quoted message.

[github-actions]

Size Change: +26 B (0%)

Total Size: 318 kB

Filename	Size	Change
dist/browser.es.js	69.6 kB	+6 B (0%)
dist/browser.js	70.6 kB	+7 B (0%)
dist/index.es.js	69.6 kB	+7 B (0%)
dist/index.js	70.6 kB	+6 B (0%)

ℹ️ View Unchanged

Filename	Size
dist/browser.full-bundle.min.js	37.6 kB

_{compressed-size-action}