Token decimals - manual correction of contract metadata

[tomasklim]

@tomasklim yes, it is reported incorrectly by Blockbook because the contract self describes itself incorrectly (probably does not implement the get decimals method and Blockbook then defaults to 18). I will have to implement manual correction of contract metadata.

trezor/trezor-suite#8030

Same tx on etherscan and blockbook
https://etherscan.io/tx/0xa7b635ff1f823fa3a99ac2353a14bfc523ce6b690b9743992757346ad8c9def9
https://eth1.trezor.io/tx/0xa7b635ff1f823fa3a99ac2353a14bfc523ce6b690b9743992757346ad8c9def9

According to blockbook, decimals = 18 https://eth1.trezor.io/api/v2/address/0xC19B6A4Ac7C7Cc24459F08984Bbd09664af17bD1
Acording to ethscan decimals = 0