fix(TransactionSyncWorker): improve stream response handling

[Alex-Werner]

Issue being fixed or feature implemented

There are several UTXO related bugs:

• Transaction is rejected: tx-txlock-conflict
• Not enough balance (0) to cover burn amount of 5
• utxosList must contain at least 1 utxo

Also, Due to a bug in grpc-js explained here. A temporary solution is used to bypass this bug until a fix is merged into Node.js explained here

What was done?

• moved handlers to their specific file
• added event-based queue async processing for stream chunks
• bip44 to correctly generate by type (internal, external)
• wrapped up stream.cancel into setImmediate

How Has This Been Tested?

• added additional tests

Breaking Changes

Fixed a generated value that was faulty as only representing external generated. Any dependency to generated from ensureAddressesToGapLimit utils will need to be updated.

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated relevant unit/integration/functional/e2e tests
• I have made corresponding changes to the documentation

For repository code-owners and collaborators only

• I have assigned this pull request to a milestone

[lgtm-com]

This pull request introduces 1 alert when merging e02a685 into 19a3f68 - view on LGTM.com

new alerts:

• 1 for Unused variable, import, function or class

[shumkov]

Good job, guys! 👍