[New Tx History] Fetch transaction list first, then status

[brtkx]

Refactoring is required to fetch the transaction list first, display them and update the status separately. This way we can show a loader on the status column, while user is able to see all of their transactions.

This is particularly useful when Orbit transactions (which are much slower) are being fetched alongside Mainnet transactions. We don't want to block displaying the Mainnet transactions and have the tx history be very slow in general.

Because getting the transactions themselves is fast (getting their status is slow for Orbit chains), we can display them first and then update the status.