fix: filter out 0 liquidity assets and order by market cap

[NeOMakinG]

Description

I noticed the scammy assets are coming from portal, they are added by 2 ways:

• Asset generation (removed them by filtering 0 liquidity assets)
• Upsert at runtime when building the portfolio (removed 0 liquidity assets too)
• Sorting by market cap in the search too, so bigger market cap assets are upper in the three)
• Avoid upserting asset we didn't manage to get market data for

Issue (if applicable)

closes #8139

Risk

Low

High Risk PRs Require 2 approvals

What protocols, transaction types, wallets or contract interactions might be affected by this PR?

Testing

• Try with demo mode, search for assets in the trade assets modal (USDC, USDT...)
  -- You shouldn't see any scammy tokens
• Try with any other big wallets, likes shapeshiftdao.eth, or your own
  -- You shouldn't see any scammy tokens

Engineering

n/a

Operations

n/a

• 🏁 My feature is behind a flag and doesn't require operations testing (yet)

Screenshots (if applicable)

Before

After

[woodenfurniture]

Suggested change

	// but we actually can't - this would rug the triple-sorting
	// but we actually can't - this would rug the double-sorting

[woodenfurniture]

@NeOMakinG a couple questions on this one:

1. When the market data for the asset list is loading, what is the expected behavior? Should we hide the assets for safety, or what is that intended behavior?
2. Is there a follow-up planned for asset sorting offline to avoid runtime cost of sorting by market cap?