Solana support

[chris13524]

Depends on reown-com/reown-rust#61

In addition to updating this dependency, Notify Server itself expects eip155 in a few places:

• notify-server/src/model/types/account_id.rs

  Line 50 in aa855db

  if is_eip155_account(s) {

• (Depends on the above assertion)

  notify-server/src/utils.rs

  Line 20 in 5b76303

  let known_skippable_prefix_len = "eip155:1".len();

• notify-server/migrations/20240111200929_unique_account_address.sql

  Line 4 in 5b76303

  RETURN lower(split_part(account_id, ':', 3));

These restrictions are in-place partly as offensive programming and in order to get a generic address which can be treated agnostic to a specific chain. When supporting Solana we need to implement chain-agnostic support as well. This could be a good opportunity to:

• Remove the function index for address, in-favor of a new unique column that stores the address (regardless of chain)
  • This would also make feat: seq implementation #273 easier
• Normalize to ERC-55 in the database (already normalized) and reject non-ERC-55 requests (Detect if there is ERC-55 non-compliance #364)
• Lookup using address column, and the address from the SIWE message rather than the computed account ID