nwc: handle stale client state cleanly and skip reverted-duplicate records

Three small NWC robustness fixes that surfaced from the Apr 29
double-credit cleanup:

- fail loudly when an NWC request references a pubkey whose user record
  no longer exists (migrated/deleted account); previously crashed inside
  handle() on `user.id`
- swallow `pubkey not found` and `user not found` in the per-event catch
  so deleted-app/migrated-user spam doesn't fill the error log — these
  are client-side staleness, not server faults
- use gf() instead of g() when fetching payment records (consistent with
  the rest of the codebase: arc fallback for wiped main-db pointers)
- filter `revertedDuplicate` payments out of list_transactions so
  clients never see the doubled records that were later reverted

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>

0 files changed, 0 insertions, 0 deletions