Show the check run on the set view and submit an open set #2603

Part of #2422 (F-DSK). Follow-up to the set view (#2574): the check results that #2575 now stores with each set (CHK-03, DSK-03), and submitting an open set from the desk.

Scope

• Set view, Checks card, from IChangeSetChecks.GetAsync:
  • The latest run: its number, overall status, when it finished, whether it ran inline or as a job, and its model cost.
  • Each checked item: every check's status (pass, warn, fail, needs review), severity and findings, each with its message, field pointer and excerpt. Failing results come first.
  • Problems that kept the engine from checking an item.
  • While the run is still going, the job's progress instead.
• Set view, Review panel: an open set offers Submit for checks (shortcut S). It calls IChangeSetChecks.SubmitAsync, which moves the set to checks running and runs or enqueues its checks. It is guarded by the moved-on check, like the other actions. A person needs this for the revert sets they open, and for the sets the generated forms will open (F-FRM F-FRM: Generated forms as the human fallback editor #2426).
• Strings through IStringLocalizer, logical utilities only, components from Components/Ui only.

Out of scope

• The routing decision: waits for Add routing rules and their evaluation #2565.
• Reopening a failed set: whoever opened it reopens it, which agents do by tool.

Acceptance

• A set whose terms check fails shows the check, its fail status, severity and the finding with its pointer. A set with no active checks shows a passed run with no results.
• Submitting a person's open set runs the checks and moves the set on, and the page shows the result.
• Integration tests pass, and the axe check still passes on the set view.