* feat: Add visible history alert to encrypted rooms.
- Adds a dismissable alert that is displayed whenever the user opens a
room with `history_visibility` != `joined`. When cleared, this is
recorded in the app's data store.
- When opening a room with `history_visibility` = `joined`, this flag is
cleared.`
Issue: https://github.com/element-hq/element-meta/issues/2875
* chore: Fix linting issues.
* feat: Move alert showing logic into state presenter.
* chore: Fix linting issues.
* tests: Fixup tests.
* feat: Use real link.
* chore: Update license header.
* chore: Add (c) to license headers.
* chore: Add `.` to license header.
* feat: Lock alert behind history sharing developer setting.
* ci: Trigger record screenshots
* feat: Create repo key using session ID for multi-account support.
* feat: Use session ID hash for constructing data store.
* tests: Correct and update tests.
* tests: Update snapshots.
* feat: Prevent identity alert from displaying with history visibility alert.
* feat: Tidy up HistoryVisibleStatePresenter logic, update previews.
* chore: Remove unused import.
* chore: Update screenshots.
* feat: Add translation string.
* chore: Remove redundant temporary translation file.
* Load `JoinedRoom` in `HomeFlowNode.navigateToRoom`, then pass it to the next navigation nodes
* Add delayed loading indicator for cases when loading the room takes too long
* Avoid an extra FFI call in `RustRoomFactory`.
Use `RoomInfo.membership` instead.
Also use `computation` dispatcher, since it should reduce the delay when switching contexts.
* Remove the dispatcher usage when loading the room in `HomeFlowNode`, we immediately call a method that changes the dispatcher used
* Make sure only a single room is opened at a time
* Create `:libraries:recentemojis` and move `AddRecentEmoji` and `GetRecentEmojis` there
- Make sure `GetRecentEmojis` won't return duplicate or invalid emojis.
- `ActionListPresenter` now handles merging suggested and recent emojis, not `ActionListView`.
* Separate thread notifications into their own notifications when the feature flag is enabled.
Otherwise, set the `threadId` to null so it'll behave as usual. It's done this way to avoid having to inject `FeatureFlagService` in several places.
* Add permalink navigation to threads from notifications, focusing on the latest event in the list of messages of the notification tapped
* Fix redactions in threads
* Clear notifications for a thread when visiting it
* Fix opening a thread happening twice, first because of the `openThreadId` value, then because of the `focusedEventId` one
* Make opening a room through a notification also focus on the latest event
* Add helper `NotificationCreator.messageTag` function
* Remove unused `ROOM_CALL_NOTIFICATION_ID`: `FOREGROUND_SERVICE_NOTIFICATION_ID`+ `ForegroundServiceType` is used instead
* Simplify `DefaultDeepLinkCreator`
* Make sure the main timeline focuses on the thread root id too when navigating to a thread
* Handle "Mark as read" action for thread notification, using `timeline.markAsRead`
* Log failures to mark rooms as read using the notification action
---------
Co-authored-by: Benoit Marty <benoit@matrix.org>
* Add `Timeline.markAsRead` to avoid reinstantiating the timeline using `Room.markAsRead`
* Mark as read when exiting the room screen, destroy the timeline when fully closed
* Ensure `MarkAsFullyReadAndExit` event can only be processed once
* Fix `DelayedVisibility` not being displayed in previews
