Fix/thread loading bug and message update bug

[nhannah]

Because the SDKs rely on the current message state to determine when and what they should reload there were multiple edge cases currently present that could cause issues with loading. Updates, and deletions to both messages and thread messages could add to the message list messages which were out of sync with the current desired state. These caused the loading logic to function incorrectly as it is dependent on the currently loaded state for pagination.

This situation also arose with messages in that are shown both in a thread and in the main channel. They would be loaded for the main channel but also added to the thread, these randomly added thread messages could cause the loading logic for threads to also get out of sync.

These fixes address these edge cases to keep a state more inline with that desired by the SDKs and users.

[github-actions]

Size Change: +1.83 kB (0%)

Total Size: 233 kB

Filename	Size	Change
dist/browser.es.js	50.7 kB	+437 B (0%)
dist/browser.full-bundle.min.js	28.8 kB	+96 B (0%)
dist/browser.js	51.3 kB	+428 B (0%)
dist/index.es.js	50.8 kB	+438 B (0%)
dist/index.js	51.4 kB	+429 B (0%)

_{compressed-size-action}

[AnatolyRugalev]

@nhannah we have upcoming changes regarding this exact problem from the backend, so let's not rush merging this as this may fix issue without SDK changes

Never mind, this is a different issue