fix: comportement on new address with existing transaction in store

[Alex-Werner]

Issue being fixed or feature implemented

When we import a transaction and one of it's constitutive element (input or output) impact and address that we own but are not yet aware of it (because it exceed the BIP44 spec on first run, for instance on an index 21).
We will submit for insertion again, but we where preventing any processing as we already had it.
This PR fixes that issue.

What was done?

• refactored BIP44.ensureEnoughtAddress so utils are splitted in separate file
• ensure importTransaction re-process a transaction on addresses that are not marked as already having it (address.transactions[])

How Has This Been Tested?

This specific case (us paying to ourself with a gap of address) were not included in test and will require to add it in our Tests improvement PR coming soon.

Breaking Changes

None.

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

[shumkov]

LGTM 👍