feat: Storybook stories for StatusBadge, StreamCard, StreamCreationForm

[stonesjarvis3]

Summary

Adds comprehensive Storybook stories covering every variant and state of the three target components, enabling contributors to develop and review UI in isolation without running the full app.

Stories Added

UI/StatusBadge (15 stories)

• All 6 lifecycle statuses: Active, Paused, Completed, Ended, Cancelled, Scheduled
• Unknown/fallback gray badge
• Compact variants for all statuses
• AllStatuses and AllStatuses (compact) side-by-side overviews

UI/StreamCard (16 stories)

• Status variants: Active, Paused, Completed, Cancelled, Scheduled
• Loading skeleton state
• Selected (bulk-checked) state with green border
• Clone action + selection checkbox combined
• Token variants: XLM, USDC, AQUA
• Time-sensitive states: Expiring soon (1 h), Long-running stream
• Edge cases: Zero flow rate, Minimal props (no timestamps)
• Light/dark background comparison

UI/StreamCreationForm (15 stories)

• Step 1 — Recipient (empty and pre-filled)
• Step 2 — Amount & Duration (empty, pre-filled, USDC token)
• Step 3 — Preview (standard and large deposit)
• Step 4 — Confirm
• Transaction overlays: Building, Signing, Submitting, Confirming, Done ✓, Error

Configuration Fixes

• .storybook/tsconfig.json: Added explicit exclude override so the parent tsconfig's **/*.stories.* exclusion does not suppress story compilation
• .storybook/main.ts: Intersected StorybookConfigVite from @storybook/builder-vite so the viteFinal hook is correctly typed

Verification

• npx next lint --file components/StatusBadge.stories.tsx --file components/StreamCard.stories.tsx --file components/StreamCreationForm.stories.tsx → ✔ No ESLint warnings or errors
• npx tsc --noEmit --project .storybook/tsconfig.json → 0 errors in story files (pre-existing errors in unrelated files are unchanged)
• npx storybook build → succeeded, 46 stories compiled and emitted to storybook-static/

Closes #489

[vercel]

@stonesjarvis3 is attempting to deploy a commit to the Chuks7 Team on Vercel.

A member of the Team first needs to authorize it.