[ingvarch]

What changes

Watch a deploy until it ends (#86), two commits.

• w on a job opens Deploy (Job: web, Version: 7) for the version the job runs. It is the deployment screen of that version, with the keys of the deployment (promote, fail, pause) and of its allocations, and two lines above its groups:
  • the newest evaluation of the job: its status, and why it could not place when it could not;
  • how the deploy stands: Waiting for the deployment of version 7., running with Nomad's description, Deployment successful., or failed and cancelled with their description. A job of a type without deployments (batch, sysbatch), or a version whose evaluation completed without one (a stopped job, an update strategy of no parallel allocations), says web has no deployment for version 7: its allocations are below.
  • Without a deployment the table holds the job's allocations at that version, and l reads only theirs.
  • A newer version submitted while the watch is open does not take its place: the watch keeps its version, and shows its deployment cancelled when Nomad cancels it.
• After y on a plan of an edit or a revert, urga goes back to where it started, says it was submitted, and opens the watch of the job on top. esc leaves it; the deploy goes on. A periodic or parameterized job, whose launches deploy and not the job itself, opens no watch, as w is not offered on it.
• The screen is read the usual way: the version, the newest evaluation, the deployments of the job and the allocations, each in the job's namespace; the event stream of the job, its allocations, deployments and evaluations only says when to read again. The evaluation is read before the deployments, so a deployment the scheduler writes between the two reads is not missed.
• docs/keys.md and docs/jobs.md describe it.

Closes #86

Checklist

• The test for this change was written first and failed
• make check is green
• The title is a conventional commit: feat(ui): ..., fix(nomad): ...