Unsent manual request keeps a blocked payment reservation #1106

The manual incoming Bitcoin payment path reserves an allowance-ledger attempt before on-chain admission. A retained unrelated payment can then reject the new request before its broadcast callback, but SendConfirmationView handles that unresolved error by recording the new reservation as UNKNOWN. Its journal has no transaction ID/payment hash, so retry can remain blocked.

The path is present on master 07610b3: OnchainSendAttemptService rejects at admission, while SendConfirmationView treats every unresolved attempt error as the current payment's uncertain outcome. This matches the independently reproduced Android #1656 review finding. iOS native reproduction has not been run by the author.

Carry known blocker ownership from admission, release only the definitely unsent different request's reservation/preparation, and keep the original recovery route. Preserve same-request, unknown/unreadable state, fresh authorization and duplicate-payment protection.