feat(frontend): add event type filter pills to ActivityHistory

[aazminu]

Description

Adds client-side event type filter pills (All, Created, Withdrawn, Topped Up, Paused, Cancelled) at the top of ActivityHistory (frontend/src/components/dashboard/ActivityHistory.tsx) so users can filter the activity timeline by stream lifecycle event type.

Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📚 Documentation update
• 🔧 Refactoring (no functional changes)
• ⚡ Performance improvement
• 🧪 Test addition or update

Related Issues

Closes #1641
Fixes #1641
/claim #1641

Changes Made

• Added and exported ACTIVITY_FILTER_OPTIONS (All, Created, Withdrawn, Topped Up, Paused, Cancelled) and ActivityEventFilter in frontend/src/components/dashboard/ActivityHistory.tsx.
• Defaulted the active filter to "ALL" and rendered accessible filter pill buttons (role="group", aria-label="Filter activity by event type", aria-pressed) alongside the Export CSV control.
• Filtered the rendered activity items (both standard and virtualized views) client-side based on selectedFilter, displaying the empty state message ("No activity found for this filter.") when no events match.
• Added unit tests in frontend/src/components/dashboard/ActivityHistory.test.tsx verifying default "All" selection, immediate filtering across event types, and empty state rendering when no events match.

Testing

Test Coverage

• Unit tests added/updated
• Integration tests added/updated
• Manual testing performed

Test Steps

1. Run npx vitest run src/components/dashboard/ActivityHistory.test.tsx src/__tests__/a11y.test.tsx in frontend/ (14/14 tests pass).
2. Run npx tsc --noEmit in frontend/ (0 errors).
3. Run npx eslint src/components/dashboard/ActivityHistory.tsx src/components/dashboard/ActivityHistory.test.tsx in frontend/ (0 errors).

Checklist

• My code follows the project's style guidelines
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have checked for breaking changes and documented them if applicable

Additional Notes

Payout Details

• USDT/USDC Receiving Wallet (EVM / ERC-20 / Polygon / Arbitrum / Optimism / Base / BSC): 0x9a51790aC01c54184bcFa067bC38f7F0E7C6F6B6