[Bug]: Issues observed while import of several custom tokens

Describe the bug

Token Import Observations:

A. BOB::
Unable to Import token:

• Avalon Avalon SOLVBTCBBN -- Symbol too long (14 chars, max 11)
• Ether -- Token address is all zeros (invalid)
• Hybrid Bitcoin -- Symbol too long (16 chars, max 11)

B. Etherlink Mainnet::
Logo Issue:

• SOGNI -- No image element found in UI (token may not be visible)
• CNDY -- No image element found in UI (token may not be visible)

C. Injective::

• Logo not displaying for stINJ, Wrapped INJ, Bitcoin Silver, Procter & Gamble Company, yINJ

D. Rootstock Mainnet::
Unable to import below tokens:

• RNS, INV, rRFOX due to : This token is an NFT. Add on the Import NFT page
• Logo not displaying for stRIF,Wrapped RBTC on RSK

E. Matchain::

No logoURI in tokenlist not accessible for below tokens:

• LaughingOutLoud,Business Alliance Coin,Miner Drop,DONOTFOMO,Matchain x PSG Points,FireGhost,OverMatch,MAT Token,Staked MAT, INCASWAP

F. Apechain:

Logo validation failing as its having URI like:

• ”logoURI”: "BASE_URL/assets/bidx500.jpg",

G. Berachain:
Token Import failing due to below error:

• BERA-- Token address is all zeros (invalid)
• pumpBTC.bera-- Symbol too long (12 chars, max 11)
• KODI WBERA-POLLEN -- Symbol too long (17 chars, max 11)
• HyperBERA.USDC--Symbol too long (14 chars, max 11)
• IV-WASABEE-4-WBERA-wgBERA-- Symbol too long (25 chars, max 11)
• IV-WASABEE-3-WBERA-iBERA --Symbol too long (24 chars, max 11)
• KODI iBERA-osBGT --Symbol too long (16 chars, max 11)
• KODI yBGT-yBERA -- Symbol too long (15 chars, max 11)
• KODI brBTC-uniBTC--Symbol too long (17 chars, max 11)
• primeLiquidBeraBTC--Symbol too long (18 chars, max 11)
• primeLiquidBeraETH--Symbol too long (18 chars, max 11)
• satSolvBTC.BERA--Symbol too long (15 chars, max 11)
• STICKY eWBERA-4-wgBERA--Symbol too long (22 chars, max 11)
• STICKY NECT-HONEY--Symbol too long (17 chars, max 11)
• KODI avUSD-HONEY--Symbol too long (16 chars, max 11)

Expected behavior

No response

Screenshots/Recordings

No response

Steps to reproduce

Verify import of the mentioned custom tokens.

Error messages or log output

Where was this bug found?

Internal release testing

Version

13.44.0

Build type

None

Browser

Chrome

Operating system

MacOS

Hardware wallet

No response

Additional context

No response

Severity

No response

Start by reproducing the listed custom-token imports in the token import flow on version 13.44.0, covering the named networks and the symbol, address, NFT, and logo cases. Compare the observed failures with the expected import and display behavior; done means the reported tokens either import and show logos correctly or receive the intended validation outcome.