fix(flashcard): stop logging withdraw parameters from NFC reads

[islandbitcoin]

Why

app/contexts/Flashcard.tsx logged the LNURL-withdraw k1 and callback on every payment tap, the card's LNURL on every balance read, and the raw error object on failure. An axios error embeds the request URL, which carries the card's p/c parameters. Together those values authorise a withdrawal from the card, and there is no transform-remove-console in babel.config.js, so they ship in release builds too.

What

• Remove the four debug dumps (k1, callback, LNURL, balance).
• On the two failure paths, log only the error message via a small errorMessage helper instead of the whole error.
• Add __tests__/contexts/flashcard-no-withdraw-logging.spec.tsx: drives both tap paths (payment and balance) and the fetch-failure path through FlashcardProvider with the NFC, lnurl and axios boundaries mocked, and asserts the parameters land in context state but never reach any console method.

No payment, custody, or NFC behaviour changes. No dependency changes. No native changes.

Adjacent logging reviewed

console.warn("Oops!", ex) at the top of handleTag catches NfcManager errors, which do not carry card parameters, so it is left alone. The redeem-lnurl-withdrawal screens log the LNURL server response (status/reason) only. Out of scope but worth a follow-up: the error toast in getPayDetails renders the raw lnurlw payload on screen.

Validation

• yarn check-code (tsc, translations, codegen, graphql) passes.
• yarn test: 97 suites, 962 tests pass.
• eslint clean on the test file; the five eslint errors on Flashcard.tsx are pre-existing lines this PR does not touch.
• Physical NFC read on TEST is still to be done: it needs a debug build on a real device plus a Flashcard tap. Tracked on the Buzz issue.

Buzz issue: 461d8d90cfa90173cf2de35e582cfd222a90e6719dcad5287094ea65dac6d479

🤖 Generated with Claude Code