Bridge deposit broken on new networks

🐛 Bug Report for zksync-cli

📝 Description

It appears that bridge deposit does not necessarily work for new networks with custom base token.

🔄 Reproduction Steps

1. Have a network with custom base token deployed with protocol v28
2. Execute

zksync-cli bridge deposit --token=BASE_TOKEN --rpc=$L2_RPC --l1-rpc=https://sepolia.drpc.org/

3. Error

Recipient address on L2 XXXXX
ⓘ There was an error while depositing funds:
ⓘ execution reverted (payload={ "id": 6, "jsonrpc": "2.0", "method": "eth_call", "params": [ { "data": "0x95d89b41", "to": "0x000000000000000000000000000000000000800a" }, "latest" ] }, error={ "code": 3, "data": "0x", "message": "execution reverted" }, code=3, version=6.14.3)

🤔 Expected Behavior

zksync-cli should not call symbol() (0x95d89b41) on 0x000000000000000000000000000000000000800a as its no longer there.

😯 Current Behavior

zksync-cli errors due to revert on call to non-existing 0x95d89b41 selector on base token contract address

🖥️ Environment

• Package version:

zksync-cli --version
1.13.0

📋 Additional Context

Reporting for partner

Start by reproducing zksync-cli bridge deposit --token=BASE_TOKEN against a protocol v28 network with a custom base token, then trace the bridge deposit entry point and the code making the symbol() call at 0x000000000000000000000000000000000000800a. Done means deposits no longer fail when that selector is unavailable; verify the command completes successfully.