Token table ordering

[mstrasinskis]

Motivation

Currently, tokens table has a fixed list of tokens considered important on top ordered (ICP, ckBTC, ckETH, ckUSDC) followed by SNS tokens ordered by creation date. This ordering seems random for new people entering the ecosystem, and only takes into account user balances after a user takes action.

Suggested order:

1. ICP is always on top regardless of user balance.
2. Tokens where a user has a higher than 0 balance:
   a. First important token list in predefined order - ckBTC, ckETH, ckUSDC
   b. Sns tokens ordered alphabetically
3. Tokens where a user has 0 balance (same sub-groups as for tokens with balance):
   a. First important token list in predefined order - ckBTC, ckETH, ckUSDC
   b. Sns tokens ordered alphabetically

Changes

• New compareTokensForTokensTable merged comparator.
• Apply sorting to sign-in and sign-out token table.

Tests

• Old tests were updated to the new order.
• Tests for new comparators.
• Test that the Token page display tokens in the expected order (ckUSDC token was added to the mock data).
• Updated the e2e test because the order changed after getting SNS tokens.

Todos

• Add entry to changelog (if necessary).

[dskloetd]

Thanks!