Deal with multiline environment variables in tests

If an environment variable has newlines in it, some of our own tests would
break due to the way we compare the output of reports with golden results.
Mangle the output of kyua a bit more so that our comparisons work.

Discovered by Travis CI builds where the non-root environment has changed
and now includes a rvm_debug environment variable that contains a function.
(Looks bogus on their side.)
Move result types out of the test_result class

Add a new model::test_result_type enum to hold all possible result types
instead of having them in model::test_result::result_type.  This is so
that we can bring in the definition of the enum type via
test_result_fwd.hpp.
Move test result type handling to dbtypes

Strip out the code to parse and generate database-level result types out
of the transactions and put this into the dbtypes module.
Extend report with a --verbose flag

The new --verbose flag causes the report command to print full details
on all selected test cases, including their metadata and their output.

This new flag replaces the previous --show-context, which by itself was
not very useful.
Verbosely report failurs in {install}check

Change "make check" and "make installcheck" to run "report --verbose"
after execution if there is a failure.  Makes for much easier debugging
and will also give insight into Travis CI failures.