Tech Titans Tackle 2024 Storage Unit Conundrum!

Revolutionary Update Ensures Accurate Determination of Storage Units, Solidifying the Future of Data Management!

Commit Details:

fix: correctly determine storage unit type (#2631) ## Why is this change needed? We're incorrectly determining that newly created storage units are 2025 storage units not 2024 storage units. ## 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 correcting the determination of storage unit types and updating related constants to reflect the correct cutoff timestamps for storage units. ### Detailed summary - Updated `UNIT_TYPE_2025__CUTOFF_TIMESTAMP` to `UNIT_TYPE_2024__CUTOFF_TIMESTAMP` in `limits.ts`. - Modified the logic in `getStorageUnitType` to return `StorageUnitType.UNIT_TYPE_2024` instead of `StorageUnitType.UNIT_TYPE_2025` for the 2024 cutoff. - Adjusted the expiry logic in `getStorageUnitExpiry` to match the updated cutoff for 2024 storage units. > ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}` <!-- end pr-codex -->