Add database merge support when newer data is detected on startup

[alexeyhramov123]

Description:
The app currently replaces the existing database on startup, even when the .db file in the log directory contains newer data.

Context:
When using Daily You across multiple devices with sync enabled, concurrent or sequential edits can occur. In this scenario, simply choosing one database version over another risks data loss.

Proposed Improvement:
If newer data is detected in the existing .db file during startup, the app should support merging changes instead of fully replacing the database. This could help preserve entries from multiple devices and make sync behavior more robust.

Expected Outcome:
Reduced risk of data loss when syncing across devices, and improved handling of concurrent or offline edits.

[Demizo]

Agreed, the current solution is poor. Merging, or tracking changes, solves both offline edits and concurrent edits. However, I hesitate on database merging as that adds a lot of complexity. Alternatively, I intend to make the syncing more visible such that the app shows the user when changes have not been synced and lets them know when there is a mismatch so that they can select which to keep. This approach does not solve concurrent edits, but it does help with offline edits and at least ensures that any data loss is manual and not automatic.