[Feature Request]: Add send-side support for BIP-353 DNSSEC proofs

BIP 353 standardises “DNS Payment Instructions”, embedding a DNSSEC proof for a human-readable name (₿alice@example.com) directly into a PSBT output.

When a host wallet resolves the name and hands the proof to a hardware wallet, Jade can independently verify the proof and display the validated name, eliminating the current hand-wavy “compare the address on-screen” UX that malware can trivially spoof.

**Current flow**
User copies a long bech32/legacy address, hopes clipboard isn’t hijacked, then “checks” the first/last characters on Jade.

**With BIP 353**
User enters a friendly name; Jade cryptographically verifies the DNSSEC proof and shows “₿alice@example.com → bc1…” (or warns if invalid).

Much of the heavy lifting can be done with the [dnssec-prover](actual link auto-removed by Blockstream for security reasons crate (no-std compatible, minimal deps)

Early Jade support would set the bar for hardware-wallet UX, much as Jade did for PSBT v2 and miniscript.