Fix web interface React 19 dependency install

[SwiftAdviser]

Summary

• update the web interface Crossmint React UI SDK and lucide-react so clean installs work with React 19
• refresh web-interface/package-lock.json so npm ci is reproducible
• fix Crossmint SDK API drift found after the install blocker was removed

What changed in the latest commit (29fe71f)

• replaced removed useAuth imports with the current useCrossmintAuth hook
• updated CrossmintWalletProvider.createOnLogin from the old signer field to the current recovery field
• added a small delegated-signer compatibility layer so the UI can build against the current wallet SDK while preserving the old flow shape
• kept API key/env handling unchanged; no credentials are added or moved in this PR

Why this matters

Before this PR, a developer following the Telegram bot quickstart could not reach the app runtime:

1. npm ci failed because package.json and package-lock.json were out of sync.
2. After the lockfile was refreshed, npm run build exposed SDK drift: removed useAuth, changed wallet creation config, and changed signer methods/types.

This PR moves the sample from install/build failure to a working local build baseline.

Validation

• cd web-interface && npm ci
• cd web-interface && npm run build with staging-safe local env values

Build result: PASS. Next.js still emits non-fatal transitive wallet-library warnings for optional @react-native-async-storage/async-storage and pino-pretty, but compilation, type-checking, and route generation complete successfully.

Scope / non-goals

• does not change Crossmint API keys, env names, or project setup instructions
• does not claim the full Telegram commerce journey is E2E complete
• full E2E still needs a disposable Telegram bot, webhook tunnel, synthetic user, capped OpenAI/SearchAPI credentials, wallet funding/payment policy, and a physical-goods sandbox

[SwiftAdviser]

Update for latest commit 29fe71f:

The original PR fixed the React 19 dependency/install blocker. After npm ci started passing, the next real blocker surfaced during npm run build: the sample was using older Crossmint React UI / wallet SDK APIs.

This commit fixes that SDK drift:

• useAuth -> useCrossmintAuth
• createOnLogin.signer -> createOnLogin.recovery
• delegated signer calls/types now build against the current wallet SDK while preserving the existing flow shape

Fresh validation:

• cd web-interface && npm ci passes
• cd web-interface && npm run build passes with staging-safe local env values

Scope note: this makes the sample install/build clean. It does not claim the full Telegram purchase journey is E2E complete; that still needs disposable Telegram/webhook/payment/fulfillment test fixtures.