[Divine-designs]

Closes #692

Summary

Adds yield transaction history filtering by asset type and date range to the history screen (the screen that actually lists yield transactions; yield-transaction.tsx is an orphaned deposit/withdraw form in this codebase).

Filter plumbing

• TransactionFilters gains an asset?: string field (src/types/transaction.ts).
• fetchTransactions applies the asset predicate client-side AND builds the corresponding backend query params (type, asset, date_from, date_to, …) ready for the live API.
• New api.getYieldTransactions({ asset, dateFrom, dateTo }) — the endpoint referenced in the issue — returns the filtered yield transaction list.

UI ((personal)/history.tsx)

• When Yield only is active, a "Filter yield history" card appears with:
  • Asset type chips: All / XLM / USDC / USDT (derived from the current result set).
  • Date range chips: All / 7D / 30D / 90D / 1Y.
• Selecting either immediately refreshes the list (client-side filter + API params).
• TransactionFilterSheet also gains an Asset chip row and date from/to inputs for custom ranges.

Acceptance Criteria

• Filter client side list using selected date range and asset filter
• Refresh API data using the selected date range and asset filter (params wired through getYieldTransactions)
• Date range + asset chips on the yield history view

Tests

• __tests__/yieldHistory.test.ts (4 cases): asset-only yield filter, date-range filter, getYieldTransactions param passing, and yield-only excludes non-yield txs.

Touched files pass tsc (no new errors), eslint, and prettier.

[drips-wave]

@Divine-designs Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[ONEONUORA]

Great job @Divine-designs