Add fluksio status, and ask for a run's parameters at a terminal

Two halves of the same gap: the CLI could start work but not show you any.

`fluksio status` draws the home screen's top half in a terminal — health and
what is wrong with it, every flow with its state and node count, and the
recent runs and failures under them. `--watch` keeps it there. Rich does the
drawing; it was already installed under fastapi's own CLI, and is named now
because a command depends on it.

`fluksio run` with no parameters at a terminal asks for them, one line per
declared input with its declared value in brackets — so Enter through the lot
is what running the defaults looks like, and an artifact input takes the
`@run:` spelling the engine now resolves. A scripted run is untouched: passing
any parameter, or piping the command, skips the questions, as does --defaults.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019V5bsYGNxcgPs4xXmTPx69

backend/tests/api/routes/test_runs.py

@@ -149,7 +149,9 @@ def made_artifact():
 
 def test_a_run_reference_resolves_to_what_that_run_produced(made_artifact):
     run_id, reference = made_artifact
-    resolved = resolve_references(artifact_flow(), {"dataset": f"@run:{run_id}.dataset"})
+    resolved = resolve_references(
+        artifact_flow(), {"dataset": f"@run:{run_id}.dataset"}
+    )
 
     # The producer's own reference, file name and all — not one rebuilt from
     # the row, which carries the message name instead.