Fix DHT GetRecord query wedge on untrusted peer responses

[jsdanielh]

An untrusted peer could respond to a DHT GetRecord query in ways that left the query in an inconsistent state, preventing it from ever completing and wedging the requester.

This change:

• Adds DhtGetInconsistentState, DhtGetVerificationFailed, and DhtGetTimeout error variants.
• Introduces abort_dht_get() which finishes the query, clears intermediate state, and surfaces the failure to the waiting channel.
• Aborts the query on verification failure, inconsistent state, and timeout, instead of silently dropping progress events.
• Ignores stale progress events for queries that are no longer tracked.

Depends on #3707 (Fix for DHT query poisoning) — this builds on the store_dht_record / query-state refactor introduced there.

Pull request checklist

• All tests pass. The project builds and runs.
• I have resolved any merge conflicts.
• I have resolved all clippy and rustfmt warnings.