RPC Wallet tests fix

[FreakyMaryk]

PR intention

RPC Wallet tests fix for:

• wallet-dump
• walletbackup
• wallet-hd

Code changes brief

Time of tests executing was increased due to tests long-run (restarting/sync/dampwallet)
There are some TODO in this tests which are can be removed during review.

[lgtm-com]

This pull request introduces 3 alerts when merging a32e423 into 53fb75c - view on LGTM.com

new alerts:

• 3 for 'import *' may pollute namespace

[ultimaweapon]

@FreakyMaryk could you provide the example of wallet dump file?

[lgtm-com]

This pull request introduces 3 alerts when merging a873714 into 53fb75c - view on LGTM.com

new alerts:

• 3 for 'import *' may pollute namespace

[riordant]

LGTM

[lgtm-com]

This pull request introduces 3 alerts when merging e23965b into 53fb75c - view on LGTM.com

new alerts:

• 3 for 'import *' may pollute namespace

[FreakyMaryk]

@ultimaweapon
wallet.unencrypted.dump.txt

[thebevrishot]

@riordant # - As wallet encryption creates a new master seed, it adds another set of hdmint keys. Could new keys can be used? Is this a bug?

[riordant]

@thebevrishot Not a bug. When you generate a new wallet, it is in unencrypted state, and has a particular master seed. When you encrypt, it generates a new master seed. Both seeds generate 21 keys to be used for mints. The newer keys will always be used, that is, the keys for latest master seed will always be used for new mints.

[lgtm-com]

This pull request introduces 7 alerts when merging 7ccaccd into d159d4c - view on LGTM.com

new alerts:

• 6 for Asserting a tuple
• 1 for Unused local variable

[lgtm-com]

This pull request introduces 1 alert when merging 142e9dd into d159d4c - view on LGTM.com

new alerts:

• 1 for Unused import

[riordant]

LGTM