"Revolutionizing Debugging: New Metrics System Deployed for RPC Server!"

"Game-changing enhancements introduced to monitor spikes in RPC calls, paving the way for efficient problem-solving and performance optimization."

Commit Details:

chore: add metrics for rpc server (#2357) It would be useful to know when there are spikes in certain kinds of rpcs for debugging purposes. ## 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 the monitoring of RPC calls in the `Server` class by integrating `statsd` metrics to track the count of open RPC requests for various methods. ### Detailed summary - Added `statsd().increment` for tracking open request count at the start of multiple RPC methods. - Added `statsd().decrement` for tracking open request count at the end of the same methods. - Methods updated include `getInfo`, `stopSync`, `forceSync`, `getCurrentPeers`, `getSyncStatus`, and many others. > ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}` <!-- end pr-codex -->