Code Conundrum Cracked: Developers Enhance Database Resilience!

New Error-Handling Measures Implemented to Log and Address Missing Merge Messages, Ensuring Smooth Operations!

Commit Details:

fix: Catch and log errors if conflict messages are not found while merging (#1801) ## Motivation Catch errors if there is an inconsistency in the DB and log it so we can get to the bottom of it. ## Merge Checklist _Choose all relevant options below by adding an `x` now or at any time before submitting for review_ - [X] PR title adheres to the [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/) standard - [X] PR has a [changeset](https://github.com/farcasterxyz/hub-monorepo/blob/main/CONTRIBUTING.md#35-adding-changesets) - [X] PR has been tagged with a change label(s) (i.e. documentation, feature, bugfix, or chore) - [ ] PR includes [documentation](https://github.com/farcasterxyz/hub-monorepo/blob/main/CONTRIBUTING.md#32-writing-docs) if necessary. - [X] All [commits have been signed](https://github.com/farcasterxyz/hub-monorepo/blob/main/CONTRIBUTING.md#22-signing-commits) <!-- start pr-codex --> --- ## PR-Codex overview This PR fixes the issue of inconsistent database entries by handling exceptions and logging warnings for missing messages in the store. ### Detailed summary - Renamed `existing_remove` to `maybe_existing_remove` and `existing_add` to `maybe_existing_add` - Added handling for missing messages in the store with logging warnings - Updated error handling for `existingRemove` and `existingAdd` in TypeScript code > ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}` <!-- end pr-codex -->