ZEVA 2 - Activity Feed

**Describe the task**
Implement an Activity Feed that provides internal users with visibility into recent activity across the ZEVA system.

The Activity Feed will serve as a centralized location where users can review record activity, status changes, and other significant actions without having to open individual records.

The Activity Feed will display activities that occurred within the previous 30 days and allow users to search and filter activity records to quickly locate relevant information.

**Purpose**
Provide IDIR users with a consolidated view of recent system activity to improve record tracking, increase visibility into business processes, and reduce the need to manually review individual records for updates.

[Figma dashboard and all activity designs ](https://www.figma.com/design/7Qgou3rxcHHk5qbmD9538x/ZEVA-2?node-id=3575-14488&t=x1GjBuNqzNdy3XTF-1)

**Acceptance Criteria**
- [ ] An Activity Feed page is available to IDIR users from Dashboard

- [ ] The Activity Feed displays all activity records in a table.
- [ ] The table displays Activity Type, Record ID, Record Type, Supplier, Performed By, Date and Time.

- [ ] Users can search activity records.
- [ ] Users can filter activity records by Activity Type, Supplier, Record Type, Date Range.
- [ ] Activity records are displayed from newest to oldest.
- [ ] The Activity Feed displays activities from the previous 30 days only.
- [ ] Activities older than 30 days are removed from the Activity Feed.
- [ ] The Activity Feed should capture significant actions performed within the system, including but not limited to: Submitted, Approved, Rejected, Returned, Recommended Approval, Any Status Changes, Any Record Updates
- [ ] Activities older than 30 days are removed from the Activity Feed view.
- [ ] Historical activity records are not deleted from the system.
- [ ] Historical activity remains available within the associated individual record history.
- [ ] Record ID values should function as links. Selecting a record takes the user directly to the associated record.

Start by reviewing the existing Dashboard entry point and the linked Figma activity-feed designs. Trace how activity records and individual record history are currently represented, then define the page, table, search, filters, links, retention view, and status/update events against the acceptance criteria. Done means IDIR users can access the feed and all listed behaviors work without deleting historical record history.

Written by the indexing model from the issue text.