Revolutionary Update Unclogs Validation Bottleneck in Code Merges!

New Commit Streamlines Error Handling, Preventing Clash of Invalid Merge Messages and Enforcement Strictures!

Commit Details:

fix: Validate merge messages only when storing messages (#1957) ## Motivation This avoids a Catch-22 where when we discover an invalid message and want to remove it we are unable to because of the validation. ## Change Summary Change validation to only occur for merge messages. ## Merge Checklist - [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. - [x] All [commits have been signed](https://github.com/farcasterxyz/hub-monorepo/blob/main/CONTRIBUTING.md#22-signing-commits) <!-- start pr-codex --> --- ## PR-Codex overview This PR focuses on validating merge messages only when storing them in the `shuttle` package. ### Detailed summary - Added conditional validation for merge messages only - Removed unnecessary commented-out code - Updated error handling for invalid merge messages > ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}` <!-- end pr-codex -->