Handle transaction hash collisions

[telezhnaya]

Same story as in near/near-indexer-for-explorer#84

Decided to create almost the same solution

[telezhnaya]

select * from action_receipts where receipt_id = "7SdPiQwWkXkNsmASztLtgHqhT52CwV19eNKKRezWCLqi";
select * from transactions where transaction_hash = "AUh97Kbbg962AfqnQTnmM7tSSy5rnczZ99xXNjAxkctL";

[telezhnaya]

I created the other solution because SingleStore requires doing so.
Now we put all the tx and receipts without the problems, but the second select gives 2 transactions.
I guess I want to think about it more.