[Bug]: Custom token import on Immutable zkEVM not working

### Describe the bug

Manual token import is not working on the Immutable zkEVM network in the browser wallet extension, returning error `Message: No XChain Swaps native asset found for chainId: 0x343b`

### Expected behavior

Click + Import tokens while connected to Immutable zkEVM and see the Custom token import field.

### Screenshots/Recordings

### Steps to reproduce

1. Add/enable Immutable zkEVM in the wallet
2. Click + Import tokens
3. See error

### Error messages or log output

```shell
Message: No XChain Swaps native asset found for chainId: 0x343b

Code: Error

Stack:

Error: No XChain Swaps native asset found for chainId: 0x343b
at s.getNativeAssetForChainId (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-0.js:1:744753)
at chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/ui-10.js:1:155933
at Generator.next ()
at chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/ui-8.js:1:5729
at Object.Pa [as useMemo] (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-10.js:1:64125)
at n.useMemo (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-10.js:1:184827)
at q (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/ui-8.js:1:5686)
at sa (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-10.js:1:59431)
at qa (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-10.js:1:68913)
at Ys (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-10.js:1:112305)
at Al (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-10.js:1:98675)
at Pl (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-10.js:1:98603)
at jl (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-10.js:1:98466)
at vl (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-10.js:1:95463)
at chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-10.js:1:45359
at n.unstable_runWithPriority (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-10.js:1:123741)
at Hi (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-10.js:1:45137)
at Yi (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-10.js:1:45305)
at Ki (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-10.js:1:45240)
at ml (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-10.js:1:92855)
at Aa (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-10.js:1:64713)
at chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/ui-10
```

### Where was this bug found?

Live version (from official store)

### Version

13.11.2

### Build type

None

### Browser

Firefox

### Operating system

MacOS

### Hardware wallet

_No response_

### Additional context

The issue is also reproducible in Chrome v.13.13.1

### Severity

_No response_

Reproduce the error in the browser extension by enabling Immutable zkEVM and selecting + Import tokens. Trace the native asset lookup that reports chainId 0x343b; done means the Custom token import field appears without the missing-native-asset error in Firefox and Chrome.

Written by the indexing model from the issue text.