feat(ansible): schedules read as sentences, each with its own page (#5332)

- The Schedules tab: a verdict line (failing first, paused, next due),
  each schedule as one line (what runs where, how often, when next, how it
  last went); the row opens its page; Run now and Pause stay in the row.
- /ansible/schedules/new and /ansible/schedules/<id>: the form on classes,
  dry run beside the button, the playbook's variables rendered with the
  page; at the foot Delete behind the confirm dialog. ?source=&playbook=
  start a new one on a playbook (Schedule it on the playbook's page).
- A run started by a schedule links to that schedule's page.
- The run page's id guard allows the Run again link's ?from=.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

steward/ansible/origins.py

@@ -24,7 +24,7 @@ def describe_origin(run, users: dict, schedules: dict, rules: dict) -> dict:
         text = f"schedule {name}" if name else "a deleted schedule"
         if who:
             text += f" (run now by {who})"
-        return {"text": text, "url": "/ansible/schedules" if name else None, "kind": "schedule"}
+        return {"text": text, "url": f"/ansible/schedules/{run.origin_id}" if name else None, "kind": "schedule"}
     if run.origin == "alert":
         name = rules.get(run.origin_id)
         return {"text": f"alert rule {name}" if name else "a deleted alert rule",