feat(v4-sdk): add max hop slippage support for multi-hop swaps

[Ayoakala]

Description

[Summary of the change, motivation, and context]

How Has This Been Tested?

[e.g. Manually, E2E tests, unit tests, Storybook]

Are there any breaking changes?

[e.g. Type definitions, API definitions]

If there are breaking changes, please ensure you bump the major version Bump the major version (by using the title feat(breaking): ...), post a notice in #eng-sdks, and explicitly notify all Uniswap Labs consumers of the SDK.

(Optional) Feedback Focus

[Specific parts of this PR you'd like feedback on, or that reviewers should pay closer attention to]

(Optional) Follow Ups

[Things that weren't addressed in this PR, ways you plan to build on this work, or other ways this work could be extended]

---

✨ Claude-Generated Content

Description

Re-adds the max hop slippage feature to the v4-sdk. This allows specifying per-hop slippage limits for multi-hop swaps, enabling finer-grained slippage control on each step of a swap route.
This PR reverts the previous revert (#470) to restore the max hop slippage functionality.

Changes

• Added maxHopSlippage optional parameter to V4Planner.addTrade() method accepting BigNumber[]
• Added maxHopSlippage: readonly string[] field to SwapExactIn and SwapExactOut types in v4BaseActionsParser.ts
• Updated SWAP_EXACT_IN_STRUCT and SWAP_EXACT_OUT_STRUCT ABI definitions to include uint256[] maxHopSlippage
• Updated parseV4ExactIn() and parseV4ExactOut() parser functions to decode the new field
• Added unit tests for per-hop slippage limits in both exactIn and exactOut scenarios
• Updated existing tests to include maxHopSlippage: [] in expected outputs

How Has This Been Tested?

Unit tests added covering:

• exactIn 2-hop swap with per-hop slippage limits
• exactOut 2-hop swap with per-hop slippage limits
• addAction with per-hop slippage limits
• Default empty maxHopSlippage when not provided

Are there any breaking changes?

No - maxHopSlippage is an optional parameter that defaults to an empty array when not provided, maintaining backward compatibility.

[github-actions]

🤖 Claude Code Review

✅ Review complete

Summary

This PR re-introduces the maxHopSlippage feature for V4 multi-hop swaps, allowing per-hop slippage limits. This was previously reverted and is now being re-added.

Changes:

• Adds maxHopSlippage: uint256[] field to SWAP_EXACT_IN_STRUCT and SWAP_EXACT_OUT_STRUCT ABI definitions
• Updates addTrade() method to accept optional maxHopSlippage?: BigNumber[] parameter
• Updates parser to extract maxHopSlippage from decoded calldata
• Adds type definitions for the new field
• Comprehensive tests for per-hop slippage functionality

Technical Notes:

• The ABI struct field order (currencyIn/Out, path, maxHopSlippage, amount...) is consistent between encoder and parser
• Defaults to empty array when not provided, maintaining backward compatibility for callers
• The addTrade() signature change is backward-compatible (new parameter is optional)

The implementation is clean and follows existing patterns in the codebase.

---

_{💡 Want a fresh review? Add a comment containing @request-claude-review to trigger a new review at any time.}

[github-actions]

📋 Review verdict: APPROVE

👆 The main review comment above is the source of truth for this PR review. It is automatically updated on each review cycle, so always refer to it for the most current feedback.

This formal review submission is for the verdict only.