Fix finished `ChatCall`s being rapidly displayed on `Chats` tab during synchronization

[SleepySquash]

Synopsis

Whenever application is being logged in, it loads the actual state of Chats user has. However, if there's many call events, the chats will rapidly display those calls as being started and then being ended.

Solution

This PR fixes some events not setting conversationStartedAt, dialing variable being ignored and fixes displaying of the already finished calls.

Checklist

• Created PR:
  • [x] In draft mode
  • [x] Name contains issue reference
  • [x] Has type and k:: labels applied
• Before review:
  • [x] Documentation is updated (if required)
  • [x] Tests are updated (if required)
  • [x] Changes conform code style
  • [x] CHANGELOG entry is added (if required)
  • [x] FCM (final commit message) is posted or updated
  • [x] Draft mode is removed
• [x] Review is completed and changes are approved
  • [x] FCM (final commit message) is approved
• Before merge:
  • [x] Milestone is set
  • [x] PR's name and description are correct and up-to-date
  • [x] All temporary labels are removed

[SleepySquash]

FCM

Debounce `ChatEventsVersioned` received in `RxChat` during `Chat`s synchronization (#1106)

Additionally:
- add `EventChatCallAnswerTimeoutPassed` handling to `RxChat`
- fix already answered or declined `OngoingCall`s appearing again during synchronization
- use `RecentChatTile.hasCall` to prevent local `ChatCall`s from being rendered as active