Improve wallet compatibility diagnostics when funding multisig contract is unsupported

[h2so4nackl-code]

Summary

The root cause of the deployment failure has already been identified: current dexdo-cli releases only accept the UpdateCustodian funding wallet, while the latest app.dex.do cabinet generates a different wallet contract.

However, the current diagnostics make this difficult to identify without inspecting the source code or comparing code hashes manually.

Current behavior

dexdo note deploy aborts before submitting any transaction because the funding multisig contract is not in the CLI allowlist.

No PrivateNote is deployed.
No transaction is sent.
No funds move.

The user only sees that deployment failed.

Expected behavior

Before aborting, the CLI should explicitly report:

• detected wallet contract type (if known);
• detected on-chain code hash;
• supported code hashes;
• whether the failure is due to an unsupported wallet contract rather than an invalid wallet or deployment error.

For example:

Unsupported funding wallet contract.

Detected code hash:
3a7a53248ff39fde936a4274eab143b5fac94feac0d8e2e2748aac5e74538d5f

Supported:
8470e1da28a2b4c742b5f7edefdd97db81c79e726f8a8b0be78d921adaf32414 (UpdateCustodian)

No transaction was submitted.
No funds were moved.

Benefit

This would allow users to immediately identify wallet compatibility issues without source-code inspection or manual comparison of contract hashes, reducing unnecessary debugging and duplicate reports.

[Futurizt]

Thanks — same root cause as #98/#99 (the note-deploy funding-wallet allowlist accepts only the UpdateCustodianMultisig code_hash). Two things: (1) a managed-wallet allowlist fix that accepts the dex.do web/cabinet wallet is reviewed and ships in an upcoming release (so the cabinet path stops hitting the wall); (2) the diagnostic itself can still be improved for genuinely-unsupported wallets (name the accepted code_hash + how to obtain a compatible UpdateCustodian wallet) — tracking that enhancement here.