Sophon 404 for bridged ETH

Nobody has claimed this yet.

### 🐛 Bug Report

#### 📝 Description

When reading the name on the beaconproxy ETH contract [Sophon testnet](https://explorer.testnet.sophon.xyz/address/0xa02dbfB2b65b4e13501d066Df432A39c6068Eded#contract) and [Sophon mainnet](https://explorer.sophon.xyz/address/0x72af9F169B619D85A47Dfa8fefbCD39dE55c567D#contract#read-proxy) it returns this error.

```
execution reverted (payload={ "id": 2, "jsonrpc": "2.0", "method": "eth_call", "params": [ { "data": "0x06fdde03", "to": "0x72af9f169b619d85a47dfa8fefbcd39de55c567d" }, "latest" ] }, error={ "code": 3, "data": "0x", "message": "execution reverted" }, code=3, version=6.13.4)
```

#### 🔄 Reproduction Steps

1. visit the links above
2. Read as proxy
3. Query `11. name`

AND

1. go to https://block-explorer-api.testnet.sophon.xyz/tokens/0xa02dbfB2b65b4e13501d066Df432A39c6068Eded for testnet
2. go to https://api-explorer.sophon.xyz/tokens/0x72af9F169B619D85A47Dfa8fefbCD39dE55c567D for mainnet

#### 🤔 Expected Behavior

On the block explorer it's expected to return `Ether` when querying the name like on [Lens mainnet](https://explorer.lens.xyz/address/0xE5ecd226b3032910CEaa43ba92EE8232f8237553#read-proxy)

AND

Return something similar to the following when interacting with the API like with [Lens mainnet](https://explorer-api.lens.xyz/tokens/0xE5ecd226b3032910CEaa43ba92EE8232f8237553)

```
{
"l2Address": "0xE5ecd226b3032910CEaa43ba92EE8232f8237553",
"l1Address": "0x0000000000000000000000000000000000000001",
"symbol": "ETH",
"name": "Ether",
"decimals": 18,
"usdPrice": null,
"liquidity": null,
"iconURL": null
}
```

#### 😯 Current Behavior

Explorer returns

```
execution reverted (payload={ "id": 2, "jsonrpc": "2.0", "method": "eth_call", "params": [ { "data": "0x06fdde03", "to": "0x72af9f169b619d85a47dfa8fefbcd39de55c567d" }, "latest" ] }, error={ "code": 3, "data": "0x", "message": "execution reverted" }, code=3, version=6.13.4)
```

API returns

```
{
"statusCode": 404,
"message": "Not Found"
}
```

#### 🖥️ Environment

Sophon testnet and mainnet. Might effect other CBTs too, but so far works on Lens

Start by reproducing the reverted `name` call from the Sophon testnet and mainnet read-proxy links, then compare both token API responses with the Lens example. Trace the explorer's token lookup and proxy-contract handling to identify the missing bridged ETH path. Done means the proxy reports `Ether` and the token endpoints return the expected ETH metadata instead of a revert or 404.

Written by the indexing model from the issue text.