EZWallet: clarify onboarding copy and add KALE ticket support

[tacticalnoot]

Motivation

• Clarify EZWallet onboarding so visitors immediately understand they can create, share, and redeem instantly redeemable tickets from the same UI and remove the ambiguous phrase about being prompted for immediate payment.
• Add first‑class KALE support so giveaways and batch tickets can be created and validated for the native KALE token alongside XLM and USDC.

Description

• Updated top-level messaging and step copy in src/experiments/ezwallet/EZWalletApp.svelte to a simple, stepwise flow (hero text, step labels, placeholders, and safety language) to improve readability for global users.
• Added KALE configuration in src/experiments/ezwallet/config.ts as KALE with issuer CB23WRDQWGSP6YPMY4UV5C4OW5CBTXKYN3XEATG7KJEZCXMJBYEHOUOV and exposed it to the app.
• Enabled KALE as a selectable asset in both single-ticket (makeOne) and batch-generation (bulk) paths inside EZWalletApp.svelte, and updated QR payload generation to emit the correct KALE issuer when chosen.
• Added KALE issuer validation to src/experiments/ezwallet/qrPayload.ts so incoming ticket payloads are checked for the expected KALE issuer.

Testing

• Ran pnpm -s check to validate type and svelte diagnostics and confirmed the changes to the EZWallet files did not introduce new EZWallet-specific failures.
• The workspace svelte-check output shows pre-existing unrelated TypeScript/Svelte errors in other components and layout files, which are unchanged by this PR.
• No runtime or end-to-end tests were run as part of this change.

---

Codex Task

[cloudflare-workers-and-pages]

Deploying smol-fe with    Cloudflare Pages

Latest commit:	f7e4d00
Status:	⚡️  Build in progress...

View logs