🔴 Resolve Token Collision Issue

[shivekkhurana]

Issue Description:

• Currently while showing tokens in wallet, we consider ticker to be unique
• Using the ticker, we group the balance across chains
• But that's not true and there might be collisions, when two tokens have same ticker.
• This will lead to incorrect grouping
• In the past, we removed these colliding tokens manually
• But with auto refresh tokens lists, this manual process has been removed
• We need to update the logic on the client side to group by name, which is truly unique, not ticker

Acceptance Criteria:

The change is not visual, so hard to test.

• The token grouping logic is updated to group by token name instead of ticker

Notes:

• @saledjenic is handling this on Desktop side, in case help is needed

[alwx]

status-go PR: status-im/status-go#6497
status-desktop PR: status-im/status-desktop#17771

[saledjenic]

Have to say that we've changed the plan a bit, and PRs referenced in the previous message will be either rebased (which will be very hard cause we've decided to add L1 chain before switching to CoinGecko and approach by using "id" and every single line will be a conflict) or reintroduced in a new PRs.

For 2.34 it was decided to solve the collision (both, symbol and decimal collisions) for the currently used tokens lists (Statsu, Aave, Uniswap) which is done in this PR status-im/status-go#6538