TRIE DB TRANSFORMATION: A BOLD MOVE IN DATA MIGRATION

Tech Titans Unleash Efficiency by Shifting Key Data from Main Database to Revolutionary TrieDB!

Commit Details:

chore: Migrate Trie data to TriDB (#1847) ## Motivation Migrate any remaining entries in the main DB for the sync trie into the Trie DB (and delete them from the main DB) ## 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) - [ ] 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 migrates trie node data from the main DB to TrieDB in the `hubble` app. ### Detailed summary - Migrates key-values to TrieDB - Adds `migrate` method to `MerkleTrie` for migration - Implements key migration logic in batches - Initiates migration in Prod environment - Deletes migrated keys from the main DB > ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}` <!-- end pr-codex -->