Currently identical to the old etc/coverage.py script, but renamed.

Signed-off-by: John Pennycook <john.pennycook@intel.com>

Using angle brackets, similar to how commands like git behave, allows us to use
metavar names that contain spaces and are easier to read.

Signed-off-by: John Pennycook <john.pennycook@intel.com>

This option enables cbicov to be run anywhere, instead of requiring it to be
run in the source directory.

Signed-off-by: John Pennycook <john.pennycook@intel.com>

Using an empty codebase means that cbicov will only generate coverage
information for files in the specified source directory.

Pre-populating the codebase file list restricts our ability to exclude files,
because files that are explicitly listed in the codebase are assumed to have
been specified by the user.

Signed-off-by: John Pennycook <john.pennycook@intel.com>

The new schema allows for coverage files to contain both a file hash
and (optional) path information.

Signed-off-by: John Pennycook <john.pennycook@intel.com>

The previous coverage schema required the exporter logic to replace all
filenames with file hashes unconditionally.

The new exporter logic is able to retain filenames, which can be used to
compute file hashes when required.

Signed-off-by: John Pennycook <john.pennycook@intel.com>

Now requires file name, a unique ID, and a different line representation.

Signed-off-by: John Pennycook <john.pennycook@intel.com>

Signed-off-by: John Pennycook <john.pennycook@intel.com>

Previously, a CodeNode could only recover region information in terms
of an extent (start line and end line) which was not sufficient to
export the information required by the new coverage format.

Signed-off-by: John Pennycook <john.pennycook@intel.com>

Signed-off-by: John Pennycook <john.pennycook@intel.com>

Signed-off-by: John Pennycook <john.pennycook@intel.com>

Handles excludes in an identical manner to codebasin.

Signed-off-by: John Pennycook <john.pennycook@intel.com>