Reevaluate Checkbox Flavors

We currently have a vast proliferation of 'flavors' of Checkbox. These serve different audiences with different needs, but the sheer number of them causes confusion. This is particularly true when dealing with official certificates, as OEMs do not know which client they need nor which tests they must pass.

We need to find a way to reduce the confusion this entails. Ideally we should have a clear view of what audience is served by each flavor, and lists of required and optional tests for each. Finally, we must have a distributable flavor of Checkbox to give to OEMs for self-testing with a clear list of requirements.

This session is likely to be boring and of limited use to anyone outside of the Canonical hardware certification team. It is simply a planning session for packaging tests for hardware manufacturers and platform daily build testing.