fix(cli): close live board rows on every exit path (#1347)

[Jaro-c]

Closes #1347

What this fixes

Six call sites across up and down opened a board row with
progress::start and never closed it on a code path that returned or
fell through, so the row sat on the working spinner forever even
though the operation was over. The plain sink emitted nothing and the
live board painted a frozen Creating / Removing / Pulling /
Stopping spinner.

The container-create side of up already does this right — it closes
with "Exists" / "Running" / "Created" before returning. The
six sites missing the close are:

Command	File	Verb before	Verb after
up	internal/engine/network/mod.rs	(stuck)	"Exists"
up	internal/engine/volume/mod.rs	(stuck)	"Exists"
up	internal/engine/build/pull.rs	(stuck)	"Failed"
down	internal/engine/lifecycle/mod.rs	(stuck)	"Absent" / "Failed"
down	internal/engine/lifecycle/mod.rs	(stuck)	"Absent" / "Failed"
down	internal/engine/lifecycle/parallel.rs	(stuck)	"Absent" / "Failed"

The failure arms in down were the most painful: a removal that
genuinely failed printed as a tracing::warn and the process exited
with the error, but the board kept painting the row with a spinner,
hiding which resource failed.

What this does NOT fix

The structural fix (a guard returned by start() that force-closes
on drop with a fallback verb) is a separate concern — the issue lists
it as a follow-up worth deciding, not as part of this fix. The per-site
fix matches the existing "Exists" / "Running" precedent on the
container-create side and fixes every observable from the bug report.

Visual: a failed row no longer looks like a successful one

Closing with the verb "Failed" is not enough on its own — the row
marker would still have been a green ✔, so a failed row would have
read as a successful one except for the word.

• internal/ui/progress/row.rs: new FAILED_MARK (✘) in red,
  selected whenever the closing verb starts with fail (case-insensitive).
• internal/ui/mod.rs: action_style now paints verbs starting with
  fail red, so the word is red too.

How it was verified

• cargo test --no-default-features --features watch,completions
  passes (1481 tests, including 3 new ones for the failed marker and
  verb band).
• cargo build clean (only the pre-existing dead-code warnings).
• cargo fmt --check clean.
• cargo clippy --lib clean of new warnings.
• Empirical against real Podman 5.7.0 on this host:
  • up then up — network + volume show Exists instead of
    staying on Creating.
  • down -v then down -v — network + volume show Absent
    instead of staying on Removing.
  • up against a non-existent image image — image row shows
    Failed instead of staying on Pulling, exit code is non-zero.

Notes

• New tests cover the closing verbs (row marker) and the red band
  (action_style). The per-site wiring is straightforward enough that
  the unit tests + empirical verification cover the change end-to-end.
• No changes to the public API. progress::start / progress_line
  keep the same signatures.