refactor: unify dispute and feed components onto shared tailwind design tokens

[s6pa1rta3n-lab]

Summary

Resolves #191 by completing the Tailwind design system unification across the remaining client components and pages:

• Unify Design Tokens: Migrated OpenDisputeModal.tsx, DisputeDetailsCard.tsx, and ActivityFeedPage.tsx from raw/slate/emerald tokens onto the canonical soil, leaf, and status-* token hierarchy matching CampaignAdminPanel, StatusBadge, FundCampaignModal, and OpenDisputeForm.
• Clean Up CampaignDetailPage: Removed orphaned dispute state/imports from earlier merges and cleanly wired OpenDisputeForm with the active campaign ID.
• Testing & Quality: Updated test mock configurations in CampaignDetailPage.test.tsx and CampaignsPage.test.tsx.

Acceptance Criteria Checklist

• All pages and components use the shared soil/leaf/status-* design-token system as the rest of the application.
• Dispute flows and cards visually harmonize with CampaignDetailPage.
• Zero contrast or accessibility regressions (verified against jest-axe / WCAG AA test suite).
• Verification checks passing:
  • npm run lint
  • npm run format:check
  • npm test (117 tests passing across 22 test suites)
  • npm run build

Payout Routing

• EVM (Base/Arbitrum/Polygon/ETH): 0xF46C9F6d70C50BF81ef3588AB523a90a594a2F89
• Stellar: GCL6OXAMLD75BMTINA6EMRUDWK5THQUSHMYNLSNBCJAPZJHNYJTUNIBC