Unleashing the Power of Monitoring: New Logging Enhancements for Event Stream

Developers Empowered to Diagnose Missed Blocks with Comprehensive Event Tracking as Commit #2620 Takes Center Stage

Commit Details:

chore: add logging for event stream monitor (#2620) ## Why is this change needed? Add logging required to debug missed blocks ## 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 enhancing logging in the `EventStreamMonitor` class to include additional context about events being processed, specifically the `eventShardId` and `currentBlockNumber`. ### Detailed summary - Added `eventShardId` to the error logging in `this.log.error`. - Included `eventShardId` and `currentBlockNumber` in the event object being logged. - Updated logging for unexpected events to include `eventShardId`. > ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}` <!-- end pr-codex -->