[Enhancement] Add Case and Case Group Filtering to Simulation Browser

[tomvothecoder]

Summary

Add Case and Case Group filters to the Simulation Browser to allow users to narrow execution results by experiment context while preserving the execution-centric design.

No schema changes required.

Motivation

The Simulation Browser is execution-focused, but users often need to:

• View all executions within a specific case
• Compare executions inside a case
• Narrow large datasets efficiently

Currently, there is no direct way to filter executions by Case or Case Group, which increases noise and reduces usability at scale.

Filtering enables contextual narrowing without changing the execution-first hierarchy.

Scope

1. Add Filters to Simulation Browser

Add the following filters:

• Case

  • Searchable dropdown or typeahead
  • Filters by case_id or case_name

• Case Group (if implemented)

  • Dropdown or searchable select
  • Filters by case_group

2. Behavior

• Filters operate at the execution level
• Filtering does not change column order or visual hierarchy
• Execution ID remains primary identifier
• Filters must be combinable with existing filters (status, canonical, etc.)
• Filtering state must persist in query parameters

3. Data Usage

• Use existing query endpoints
• No additional heavy joins beyond what is already required for listing simulations

Non-Goals

• No grouping or aggregation by Case
• No case-level summaries
• No new routes
• No schema or database changes
• No redesign of simulation tables or cards