Unify token standard/type

[tomasklim]

For some reason we introduced type to TokenTransfer object which override token standard, so standard is now located in standard attribute in case of TokenTransfer.
However, in case of TokenInfo in account, token standard is in type attribute.

Please unify.

Find out what is better, if using type from blockbook API or standard.

Do not forget about migration.

Then we will be able to get rid of this:

export const isNftTokenTransfer = (transfer: TokenTransfer) =>
    ['ERC1155', 'ERC721', 'BEP1155', 'BEP721'].includes(transfer.standard || '');

// TODO: TokenInfo should use TokenStandard type
export const isNftToken = (token: TokenInfo) =>
    ['ERC1155', 'ERC721', 'BEP1155', 'BEP721'].includes(token.type || '');

[enjojoy]

I think that it's better to name it a standard, because it's named like that in Ethereum and Solana docs and this term is commonly used.