test_plan_generator: Start writing new TestUnit fields to output

We'll dual-write for now to the new and old places, then migrate recipes
to use the new fields, then drop writing the old test units.

In the mean time, a lot of this code (and tests) look bloated, but it'll
be easy to clean that up afterward.

There's an outstanding issue of figuring out if the builds actually have
the critical field set at all. This CL assumes that the field is set,
and defaults to critical := true anyway, so there's no harm.

TEST=unit tests, local run

Change-Id: Ic191f1ad43bbf5218a3bdefe46ba289ae3be3123
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/test_planner/+/1613340
Reviewed-by: Evan Hernandez <evanhernandez@chromium.org>
Commit-Queue: Sean Abraham <seanabraham@chromium.org>
Tested-by: Sean Abraham <seanabraham@chromium.org>
6 files changed
tree: 269c47543e913894d613139bf5b027a074f01b4a
  1. .gitignore
  3. cipd.yaml
  4. deploy_cipd.json
  5. deploy_cipd.sh
  6. src/