Use block tracker to poll incoming transactions

[matthewwalsh0]

Explanation

Currently the TransactionController retrieves incoming transactions when explicitly requested via the fetchAll method meaning the cadence of polling is dictated by the client.

This PR removes the fetchAll method and instead uses the blockTracker instance provided to the controller to automatically poll for incoming transactions whenever the current network has a new block.

This polling can be started and stopped using the startIncomingTransactionPolling and stopIncomingTransactionPolling methods respectively. Or an update can be required immediately via the updateIncomingTransactions method.

Additional optional arguments have also been added to the constructor to configure the incoming transaction support.

References

Closes #965

Changelog

@metamask/transaction-controller

• BREAKING: Remove fetchAll method.
• BREAKING: Add required getSelectedAddress callback argument to constructor.
• BREAKING: Update fromBlock and limit types in RemoteTransactionSourceRequest.
• BREAKING: Add isSupportedNetwork method to RemoteTransactionSource interface.
• ADDED: Optional incomingTransactions constructor arguments including apiKey, includeTokenTransfers, isEnabled, and updateTransactions.
• ADDED: startIncomingTransactionPolling, stopIncomingTransactionPolling, and updateIncomingTransactions methods.

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've highlighted breaking changes using the "BREAKING" category above as appropriate

[vinistevam]

Amazing PR @matthewwalsh0 🚀

[legobeat]

Related: MetaMask/eth-block-tracker#169