fix(universal-router-sdk): update universal router and v4 dependency version

[dianakocsis]

PR Scope

Please title your PR according to the following types and scopes following conventional commits:

• fix(SDK name): will trigger a patch version
• chore(<type>): will not trigger any release and should be used for internal repo changes
• <type>(public): will trigger a patch version for non-code changes (e.g. README changes)
• feat(SDK name): will trigger a minor version
• feat(breaking): will trigger a major version for a breaking change

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]

[graphite-app]

Graphite Automations

"Request reviewers once CI passes on sdks monorepo" took an action on this PR • (12/16/24)

1 reviewer was added and 1 assignee was added to this PR based on Siyu Jiang (See-You John)'s automation.

[jsy1218]

UR is re-deployed on Sepolia, Base Sepolia, Arb Sepolia, and Unichain Sepolia right? Do we need to update UR v2.0 address in this file

sdks/sdks/universal-router-sdk/src/utils/constants.ts

Line 21 in 9eaff50

export const CHAIN_CONFIGS: { [key: number]: ChainConfig } = {

, in this same PR?

[jsy1218]

Also Im thinking whether we should merge #217 first. It seems like merging ur-sdk first might not break, but it's still a good practice to merge sdk-core