Use coverage checking in consensus tests

We take labelling and shrinking serious, and we check distribution of labels by hand when first checking the generators, but we do not use automated coverage checking. We should, primarily to guard against regressions. It may be worth talking to dev-ops if we can have a nightly "more expensive" test run with a higher number of tests and with coverage checking enabled where appropriate.