fix(utxo-withdraw): get hw ctx only when PrivKeyPolicy is trezor

[shamardy]

This fixes task::withdraw::init for non-trezor utxo withdraws as it was failing with "error_data": "NoTrezorDeviceAvailable"

To Test:
Make sure task::withdraw::init works fine for iguana/hd wallet/trezor

[CharlVS]

@shamardy Thank you for taking care of this so quickly. I've tested it out, and I am now getting a different error:

flutter: mm2Rpc request: {"method":"task::withdraw::init","mmrpc":"2.0","params":{"coin":"DOC","to":"RWiJB5gVjY3vRY1WWncRkUBg1vi9aRgp7P","from":{"derivation_path":"m/44'/141'/0'/0/1"},"max":true},"userpass":"45PVe8TkgwAouQKv7lqcbHqb@A1C1enC"}
flutter: RPC response: {"mmrpc":"2.0","result":{"task_id":10},"id":null}
[log] isErrorResponse: false, json: {mmrpc: 2.0, result: {task_id: 10}, id: null}
flutter: mm2Rpc request: {"method":"task::withdraw::status","mmrpc":"2.0","params":{"task_id":10,"forget_if_finished":false},"userpass":"45PVe8TkgwAouQKv7lqcbHqb@A1C1enC"}
flutter: [ERROR]: 31 12:21:27, coins::utxo::utxo_withdraw:251] INFO Trying to withdraw MAX DOC from RX5H99JPtgjXktyfQXtAgvDbe6kRiTtsAu to RWiJB5gVjY3vRY1WWncRkUBg1vi9aRgp7P

flutter: RPC response: {"mmrpc":"2.0","result":{"status":"InProgress","details":"GeneratingTransaction"},"id":null}
[log] isErrorResponse: false, json: {mmrpc: 2.0, result: {status: InProgress, details: GeneratingTransaction}, id: null}
flutter: mm2Rpc request: {"method":"task::withdraw::status","mmrpc":"2.0","params":{"task_id":10,"forget_if_finished":false},"userpass":"45PVe8TkgwAouQKv7lqcbHqb@A1C1enC"}
flutter: RPC response: {"mmrpc":"2.0","result":{"status":"Error","details":{"error":"Internal error: P2PKH script 'OP_DUP\nOP_HASH160\nOP_PUSHBYTES_20 0xeb1a21101bcf4b4ca2f727ad77dbca311d3e1cb6\nOP_EQUALVERIFY\nOP_CHECKSIG\n' built from input key pair doesn't match expected prev script 'OP_DUP\nOP_HASH160\nOP_PUSHBYTES_20 0xef12006fbbecdf69e58016de36ea3db01386e561\nOP_EQUALVERIFY\nOP_CHECKSIG\n'","error_path":"utxo_withdraw.lib.with_key_pair","error_trace":"utxo_withdraw:326] lib:150] with_key_pair:114]","error_type":"InternalError","error_data":"P2PKH script 'OP_DUP\nOP_HASH160\nOP_PUSHBYTES_20 0xeb1a21101bcf4b4ca2f727ad77dbca311d3e1cb6\nOP_EQUALVERIFY\nOP_CHECKSIG\n' built from input key pair doesn't match expected prev script 'OP_DUP\nOP_HASH160\nOP_PUSHBYTES_20 0xef12006fbbecdf69e58016de36ea3db01386e561\nOP_EQUALVERIFY\nOP_CHECKSIG\n'"}},"id":null}
[log] isErrorResponse: true, json: {mmrpc: 2.0, result: {status: Error, details: {error: Internal error: P2PKH script 'OP_DUP
      OP_HASH160
      OP_PUSHBYTES_20 0xeb1a21101bcf4b4ca2f727ad77dbca311d3e1cb6
      OP_EQUALVERIFY
      OP_CHECKSIG
      ' built from input key pair doesn't match expected prev script 'OP_DUP
      OP_HASH160

[mariocynicys]

all the utxos in the tx u wanna sign must be owned by the same p2pkh address and that address must be the activated one in the HD wallet. was that the case for the test u did? @CharlVS
oops, we actually should use the keypair of the from derivation path and not sign the tx using the activated address.

[shamardy]

@shamardy Thank you for taking care of this so quickly. I've tested it out, and I am now getting a different error:

@CharlVS please test after the latest commit.

oops, we actually should use the keypair of the from derivation path and not sign the tx using the activated address.

@mariocynicys The last commit should fix this issue.

[mariocynicys]

LGTM

[CharlVS]

Thank you, @shamardy. I've tested it and confirmed it works as expected when withdrawing between HD wallet addresses for DOC. However, I can't confirm that it works as expected for all possible parameters as QA typically does.

[shamardy]

However, I can't confirm that it works as expected for all possible parameters as QA typically does.

Will wait for @smk762 review for this. We need to make sure that trezor works as before as well.

[onur-ozkan]

changes LGTM

[shamardy]

Will merge this and @KomodoPlatform/qa can test this in dev.