Protocol Power Play: Client Library Levels Up with Snapchain Parity!

New proto definitions enhance functionality and unlock innovative features for user data management and tier handling.

Commit Details:

chore: bring protos to parity with Snapchain for client library (#2591) ## Why is this change needed? The new proto definitions need to be exposed via the client library to build on new features. ## 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) - [x] 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 updating the protocol buffers in the client library to align with the Snapchain implementation. It introduces new message types, enums, and fields to enhance functionality, particularly around tier management and user data handling. ### Detailed summary - Added `USERNAME_TYPE_BASENAME` to `username_proof.proto`. - Introduced `TierDetails` message and `tier_subscriptions` field in `StorageLimitsResponse`. - Updated error message date in `time.test.ts` to 01/01/2021. - Added new user data types: `USER_DATA_TYPE_BANNER`, `USER_DATA_PRIMARY_ADDRESS_ETHEREUM`, and `USER_DATA_PRIMARY_ADDRESS_SOLANA`. - Introduced `TEN_K_CAST` enum in `message.proto`. - Added `EVENT_TYPE_TIER_PURCHASE` in `onchain_event.proto`. - Created `TierPurchaseBody` message with relevant fields. - Updated `OnChainEvent` to include `tierPurchaseEventBody`. - Added methods for handling `TierType` in JSON conversions. - Enhanced `StorageLimitsResponse` to include `tierSubscriptions`. > ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}` <!-- end pr-codex -->