"Tech Triumph: HubSubscriber's Resilient Retry Mechanism Revolutionizes Error Handling!"

"New enhancements enable smoother server-side termination management, paving the way for a robust streaming experience."

Commit Details:

fix: handle retries on server-side termination properly in HubSubscriber (#2627) ## Why is this change needed? Previously the `HubSubscriber` would raise if the stream was closed in between when there was an error on one rpc and when the retry happened. ## 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 improving error handling in the `HubSubscriber` class by properly managing retries during server-side terminations. ### Detailed summary - Added a log message indicating an unexpected halt in the hub event stream processing. - Changed the log message for when the subscription is stopped to specify aborting the retry. - Ensured the retry logic only proceeds if the subscription is not stopped after a sleep period. > ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}` <!-- end pr-codex -->