fix: public payments polish part 1

[ben-kaufman]

Summary

• route manually entered Pubky keys through the contact flow
• route contact Pubky keys from Send scan, Send paste, QR scan, and QR paste flows instead of treating them as payment payloads
• preserve and filter contact activity correctly for RBF/replaced sent transactions
• pop the add-contact screen before opening the send sheet from contact payment routes
• fix the new-profile first-channel LN contact payment issue where iOS published a public BOLT11 before the receiver channel was actually usable, causing route not found until receiver restart
• publish public Paykit BOLT11 endpoints only after Lightning channels are usable/routable, and refresh/reconnect on channel-ready
• add focused coverage for Pubky routing helpers and RBF contact propagation

Verification

• swiftformat on touched Swift files
• git diff --check
• git diff --check origin/master...HEAD
• xcodebuild build was previously attempted with writable DerivedData/SPM paths, but SwiftPM dependency resolution hung while fetching bitkit-core and was stopped

Includes the non-UI route-not-found fix from #539 and the reviewed Pubky contact scan/paste flows. Missing/disabled UI and UI polishing follow-ups are intentionally excluded.

[piotr-iohk]

tACK

[ovitrif]

Reviewed code, LGTM.

Tested:

• send > scan contact QR ❌
• send > paste contact pubky ❌
• send > enter manually > paste contact pubky ✅
• QR > Scan ✅
• QR > Paste ❌

[piotr-iohk]

Re-tested on device. All routes work as expected now.

send > scan contact QR ✅
send > paste contact pubky ✅
send > enter manually > paste contact pubky ✅
QR > Scan ✅
QR > Paste ✅

[ovitrif]

tAck

[piotr-iohk]

Looks like the commits in this PR are not GPG/SSH signed, and branch protection requires signed commits before merge. Could you re-sign the commits @ben-kaufman?

[ben-kaufman]

@piotr-iohk updated