refactor: use single source of information for tx APIs

Nowadays APIs `/transaction` and `/thin_wallet/address_history` return transaction data that come from different methods, then can have differences. We must get information from those APIs from a single method and check if other APIs are using different methods as well

Start by locating the implementations of the `/transaction` and `/thin_wallet/address_history` APIs and compare how each obtains transaction data. Search the other APIs for separate transaction-data methods, then identify a shared source that preserves their expected responses. Done means the relevant APIs use one consistent method and their behavior is covered by the existing tests.

Written by the indexing model from the issue text.