fix(server): filter runs by command arguments

What changed

• Filters Generate Runs and Cache Runs by command_arguments instead of the command name field.
• Normalizes displayed command filter values by stripping the UI-only tuist prefix before converting filters to Flop filters.
• Adds a shared command formatter so run tables render full commands consistently, with sensible fallbacks like tuist generate and tuist cache for empty arguments.
• Updates the local seed data to generate more realistic command arguments for generate, cache, and test events.
• Adds LiveView coverage for filtering by displayed command, prefix-only tuist filters, and empty command arguments.

Why

The dashboard displays commands as full CLI invocations, but the filter was querying the short name field (generate/cache). A user filtering by what they saw in the UI, such as tuist generate --configuration DebugStaging, could therefore get no rows even when matching runs existed.

Impact

Users can now filter run lists by the command text shown in the dashboard. Local development seed data is also easier to use when checking command filters because it includes realistic command variants instead of rows that all render as bare tuist.

Validation

• mix test test/tuist_web/live/generate_runs_live_test.exs test/tuist_web/live/cache_runs_live_test.exs
• Local browser check at http://localhost:8247/tuist/tuist/module-cache/generate-runs with:
  • filter_name_val=tuist
  • filter_name_val=tuist generate --configuration Debug

Both browser checks showed matching rows with full command labels rather than the empty state.