Transaction order during bootstrap and revert

[rainydio]

Calls to TransactionHistoryService.streamByCriteria currently lack strong guarantee about transaction order. Naturally postgres will return them in order they are stored and that is historical order. Occasionally due to vacuuming order might be messed. Explicit order by is required. The best way to do that is to ORDER BY blocks.height, transactions.sequence, but postgres lacks cross-table indexes to make such ordering efficient. To deal with that block_height column has to be added to transactions table, composite foreign key can be used to ensure that block_id and block_height point to the same row. Then index over transactions(block_height, sequence) can be created and ORDER BY block_height, sequence can be executed quickly.

Later same index can also be used by API to return transactions in reverse order instead of relying on timestamp.