Updates to V1 History plugin to support FIO about fio

[ericbutz]

18-Mar-2020
The initial import of the light history implementation for FIO from Aaron:
5824c17
This included optimizations Greymass made around the deprecated history plugin and a few tweaks to improve replay speeds.

[ericbutz]

18-Mar-2020 - From Eric Butz
Issue where the initial transaction does not show up for the

1. On Testnet Monitor, create a new key pair
2. Use the faucet to fund the account using the public key. Copy the transaction ID number.
3. Go to a block explorer ( https://explorer.testnet.fioprotocol.io ) and search on the account name. You will see that no transactions are listed for that account.
4. If you enter the txn ID into the explorer, you see the details in the Blockchain Raw Data.
5. If you search on the "fio.token" account in the block explorer, you will see the "newaccount" action.
   We are wondering if there may not be an update to the history plugin code that could serve as a short term solution to somehow capture that action.

Greymass response:
So, a heads up on my thoughts for this:
the function that determines who gets "notified" in history is here:
https://github.com/fioprotocol/fio/blob/master/plugins/history_plugin/history_plugin.cpp#L186-L205

This creates a set of accounts which will contain effectively a pointer to the corresponding action/transaction. Because the account doesn't exist during its creation during the pub key, it wouldn't be a part of that set.

What I suggest is inside that function do the following;
Check if (at.act.name == N(newaccount)) in that function, and if so, decode the corresponding action, decode the account name from the pubkey, and then add that account name to the set. ( result.insert(blah))

[ericbutz]

1-May-2020 Issue with duplicate transactions for trnsfiopubkey showing up in history and the block explorer. Tracked in Issue #106

[ericbutz]

Code has been merged into Develop. Any remaining issues will be tracked separately. Closing.