[Bug]: custom network send - show a crosschain swap related error (no swap was requested) did work pre extension update

### Describe the bug

custom network send - show a crosschain swap related error (no swap was requested) and is impossible to execute

did work pre extension update without any issue

custom network settings are correct

### Expected behavior

as the action was not a swap but a send

the expected behavior is that the send on same chain work even the custom network is not supported by metamask crosschain protocol

i also found no workaround to be able do a send on this custom chain without this error

it was working perfect pre last metamask extension update

### Screenshots/Recordings

_No response_

### Steps to reproduce

add custon network:

Network Configuration:
Network Name: Diamond
RPC URL: https://rpc.bit.diamonds/
Chain ID: 17771
Symbol: DMD
Block Explorer URL: https://explorer.bit.diamonds/

claim some coins of this custom network via faucet.bit.diamonds

try make a outgoing transaction towards a address target on same network

### Error messages or log output

```shell
MetaMask encountered an error
Your information can’t be shown. Don’t worry, your wallet and funds are safe.

Error message

Message: No XChain Swaps native asset found for chainId: eip155:17771

Code: Error

Stack:

Error: No XChain Swaps native asset found for chainId: eip155:17771
at s.getNativeAssetForChainId (chrome-extension://ejbalbakoplchlghecdalmeeeajnimhm/common-0.js:5:79096)
at m (chrome-extension://ejbalbakoplchlghecdalmeeeajnimhm/ui-4.js:72:8380)
at h (chrome-extension://ejbalbakoplchlghecdalmeeeajnimhm/ui-4.js:72:8763)
at f (chrome-extension://ejbalbakoplchlghecdalmeeeajnimhm/ui-13.js:1:294018)
at sa (chrome-extension://ejbalbakoplchlghecdalmeeeajnimhm/common-10.js:1:169002)
at Qs (chrome-extension://ejbalbakoplchlghecdalmeeeajnimhm/common-10.js:1:220902)
at Al (chrome-extension://ejbalbakoplchlghecdalmeeeajnimhm/common-10.js:1:208246)
at Rl (chrome-extension://ejbalbakoplchlghecdalmeeeajnimhm/common-10.js:1:208174)
at Ol (chrome-extension://ejbalbakoplchlghecdalmeeeajnimhm/common-10.js:1:208037)
at wl (chrome-extension://ejbalbakoplchlghecdalmeeeajnimhm/common-10.js:1:205034)
at chrome-extension://ejbalbakoplchlghecdalmeeeajnimhm/common-10.js:1:154930
at n.unstable_runWithPriority (chrome-extension://ejbalbakoplchlghecdalmeeeajnimhm/common-10.js:1:233312)
at Go (chrome-extension://ejbalbakoplchlghecdalmeeeajnimhm/common-10.js:1:154708)
at Jo (chrome-extension://ejbalbakoplchlghecdalmeeeajnimhm/common-10.js:1:154876)
at Qo (chrome-extension://ejbalbakoplchlghecdalmeeeajnimhm/common-10.js:1:154811)
at zl (chrome-extension://ejbalbakoplchlghecdalmeeeajnimhm/common-10.js:1:214073)
at n.unstable_runWithPriority (chrome-extension://ejbalbakoplchlghecdalmeeeajnimhm/common-10.js:1:233312)
at Go (chrome-extension://ejbalbakoplchlghecdalmeeeajnimhm/common-10.js:1:154708)
at Il (chrome-extension://ejbalbakoplchlghecdalmeeeajnimhm/common-10.js:1:213359)
at De (chrome-extension://ejbalbakoplchlghecdalmeeeajnimhm/common-10.js:1:225573)
at Jt (chrome-extension://ejbalbakoplchlghecdalmeeeajnimhm/common-10.js:1:133452)
```

### Where was this bug found?

Live version (from official store)

### Version

13.16.3

### Build type

None

### Browser

Microsoft Edge

### Operating system

Windows

### Hardware wallet

_No response_

### Additional context

_No response_

### Severity

as we suggest to our community metamask as primary keymanagement solution
its high impact issue if send is not possible

would require us to send them to alternatives key management solutions like brave where it works without any issues

Reproduce the send on custom chain eip155:17771 using the network details and version 13.16.3, then trace the reported getNativeAssetForChainId path in the extension source. Done means a same-chain send can proceed without requiring an XChain Swaps native asset; the report names no repository tests or files.

Written by the indexing model from the issue text.