[Filters] Add filters to Search - Assets

### View
Search – Assets

### Filters to Add

- Filter by **Asset Group**
↪ Narrow results to a logical grouping of assets (e.g., `revenue_reporting`, `customer_metrics`)

- Filter by **Consuming DAG** and / or **Producing Task**
↪ Quickly locate assets by their upstream producer or downstream consumer

- Filter by **Last Event Timestamp (Range)**
↪ Identify stale or recently updated assets

- Filter by **Is Alias (Yes/No)**
↪ Distinguish between assets vs. placeholders

- Filter by **Has Events (Yes/No)**
↪ Distinguish between assets with active data lineage vs inactive definitions

### API Support

⚠️ Partial

- The `assets` API supports filtering by:
- `dag_id`, `task_id`, and sometimes `group`
- Currently lacks:
- Filtering by event presence (`has_events`)
- Range filtering by last event timestamp

### UI Impact

- Add a filter panel above the asset list table
- Useful in large deployments with hundreds or thousands of assets

### Notes

- Enables users to answer critical questions like:
- “What assets are stale?”
- “Which DAGs produce assets in this domain?”
- Especially helpful when debugging broken pipelines or validating asset freshness

Start by tracing the assets API and the Search–Assets asset list table, then compare the requested filters with the API's existing dag_id, task_id, and group support. Done means the asset list has the requested filter panel and the missing event-presence and last-event-range filtering is supported consistently across the UI and API.

Written by the indexing model from the issue text.