**Revolutionary Redis Revamp: Introducing Custom Key Prefixes for Enhanced Monitoring!**

*New update promises to streamline key management across event streams, ensuring unparalleled uniqueness and functionality!*

Commit Details:

fix: add custom redis key prefix for monitoring (#2610) ## Why is this change needed? If clients split up streams beyond host/shard, the keys in redis need a special prefix to remain unique per stream. ## 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 introduces a custom Redis key prefix for monitoring in the `EventStreamMonitor` class, enhancing key management for event streams. ### Detailed summary - Added a new property `redisPrefix: string;` in the `EventStreamMonitor` class. - Updated the constructor to accept `redisPrefix: string`. - Modified the `streamKey` method to use the new `redisPrefix` for generating keys. > ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}` <!-- end pr-codex -->