Generalize -v flag in testers

We want to start passing the configuration variables to the list operation,
should the test program want to access them, so we need to make the -v flag
"generic".

This change only moves the parsing of the -v flag to happen before the
tester's subcommand name.  The "list" command still ignores these values.
Pass user configuration variables to ATF's list

Allow access to the user-provided configuration variables from ATF test
programs when running in "list" mode.  This change affects the testers
only.
Pass user configuration variables to tester's list

Plumb through the passing of user configuration variables all the way
to the execution of the tester's "list" operation, which effectively
causes ATF test programs to have access to this data when running in
"list" mode.

This is quite complicated (and confusing at first) because the user
configuration needs to be handed to the Kyuafile parsing code, which
in turn has to inject this data into lazy_test_program so that the
variables are available when it is time to invoke the test program
for loading of test cases.
Add integration tests for config vars in headers

Make sure that user-provided configuration variables reach ATF test
programs when running in list mode by adding an integration test.
Merge branch 'issue-30'

Plumb through support to query configuration variables from ATF's
test case heads.  This resolves the confusing situation where test
cases could only do this from their body and cleanup routines.

Fixes #30.