Major Reversal in Event Stream Processing Rocks Development Team!

Unexpected Halting of Operations Leads to Urgent Fix as Developers Scramble to Restore Order and Efficiency!

Commit Details:

Revert "feat: process events from stream in order (#2616)" (#2618) This change causes the event stream to halt unexpectedly. ## Why is this change needed? Describe why this issue should be fixed and link to any relevant design docs, issues or other relevant items. ## 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. <!-- start pr-codex --> --- ## PR-Codex overview This PR focuses on reverting changes to the event stream processing, ensuring events are handled in order, and introducing the ability to claim and process stale events. ### Detailed summary - Reverted event stream processing changes for order. - Added `claimStale` method to retrieve pending events. - Introduced `eventProcessingTimeout` property in `HubEventStreamConsumer`. - Implemented `processStale` method for processing stale events. - Enhanced error handling and monitoring for event processing. > ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}` <!-- end pr-codex -->