Only adopt a funding payment's own transactions from wallet sync

Wallet sync resolves a funding payment's id for any transaction linked
to the record — through its conflicting txids or the funding outpoint
it spends — and then adopted that transaction's txid and confirmation
outright. A cooperative close conflicts with a pending splice in
exactly that way: the splice record would report the close's txid and
confirmation under its InteractiveFunding type and contribution
figures and graduate as if the splice had confirmed, while the close's
own record never received its confirmation. Adopt a transaction only
when it is part of the payment's funding history — the record's
current txid, a classified candidate, or an unclassified round
carrying the live intent's contribution (e.g. a counterparty RBF round
wallet sync sees before classification). Anything else is recorded
under its own txid-keyed id, which also delivers the close's
confirmation to the close's own record.

Generated with assistance from Claude Code.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Author: jkczyz