feat(wallet): adopt chia-query 0.10.0 exclusion + PeerOrigin in quorum probing

[MichaelTaylor3d]

DO NOT MERGE — implementation + gate round in progress.

Adopts chia-query 0.10.0 (connect_random_peer_excluding, PeerOrigin) in dig-wallet's quorum corroborator so the dig_ecosystem#2648 pool fix reaches production.

Closes dig_ecosystem#2904 (tracked on the superproject; closed by the orchestrator).

[MichaelTaylor3d]

CLOSED, not merged: the adoption is blocked by a dependency-line conflict, not by implementation work.

chia-query 0.10.0 is built against chia-protocol 0.36 / chia-wallet-sdk 0.34 (it moved off the 0.26 line at 0.9.0). dig-wallet is on chia-protocol 0.26 / chia-wallet-sdk 0.30 / chia-sdk-test 0.30, so the Peer and Message values connect_random_peer_excluding returns no longer unify with the ones dig-wallet stores in ChiaPeerSession and queries in header_hash_from. Measured, not inferred — with the pin at 0.10.0 the crate fails to compile with 4 type errors of the form expected chia_wallet_sdk::chia_sdk_client::Peer, found chia_sdk_client::peer::Peer and expected chia_protocol::Message, found chia_protocol::chia_protocol::Message.

Adopting 0.10.0 therefore requires migrating dig-wallet's whole chia stack 0.26 to 0.36, across the 7 files that touch chia_query — including sage/fallback.rs, which PR #224 owns. That is a separate, larger unit of work and a real collision, so this lane stops here rather than widening.

The adoption diff itself (exclusion + PeerOrigin filtering + a testable assemble_distinct_sample seam and three tests) is parked on the branch at 305cea1 for whichever lane performs the stack migration. Left closed so it cannot be merged, and dig-node's nightly cron publishes stable from main unattended.