Confirm, correct or reject a Bug origin #1029

Parent

#978

What to build

• thirdshift bug-origins [<issue>] [--json] lists or shows Bug origins and their state.
• Settling one: --confirm, --correct <pull request> or --none settles it.
• A confirmed Bug origin counts against its Run in Run metrics (Spec: Run metrics, the signals each Run leaves, kept apart #981). It also proposes an Eval task for Spec: Experiments, which measure a change before it reaches production #977's code-review suite, in The Eval task format, suites and time-safe repositories #1000's proposal state: the pull request's diff as it was reviewed, with a draft catch criterion. Spec: Experiments, which measure a change before it reaches production #977's approve command takes it into the suite.
• A rejected or unsettled one counts for nothing.

Acceptance criteria

• Confirming, correcting and rejecting each change the Bug origin's state, and --json shows it.
• A confirmed Bug origin proposes an Eval task, which stays out of its suite until it's approved.
• A rejected or unsettled Bug origin proposes nothing.