Generalize color codes per function and leave them empty if a "real
pipe" (i.e. pipe or file) is detected[1] on STDERR (2).

 [1]: http://stackoverflow.com/questions/911168/how-to-detect-if-my-shell-script-is-running-through-a-pipe

In this case it's simpler--no need to detect end case and no need to
shift, i.e. less typing/reading.

Now testname.oracle file can specify expected exit status file
as well, or different path for stdout/stderr oracles (default is
testname.oracle.stdout and testname.oracle.stderr)

This effectively allows for testing scenarios where exit status or error
output can be tested as well.

Now that cfgrep speed is vastly improved this test does not need
to be turned off as tedious.

Replace most of sed / grep calls with bash-native code.
Speed improved ~2x for basic tests and over 10x for games_with_spaces

Move to runner parameters -t and -s;  allow filtering based
on test name, sub-test name or both.

Add semantic exit functions and review exit statuses.

config.cfgrep does better job at hinting how the function works
(i.e. somehow similar to UNIX grep) and that the use is not limited to
INI files.

Also default config file suffix is now "conf".

 *  Add colors,
 *  print ffoo version,
 *  honor TF_DEBUG and TF_VERBOSE from environment,
 *  use nicer but smaller ASCII-art
 *  and include test name in subtest name.

"read strategy" is too ambiguous.  What is really happening is that we
are "merging" the (posible) files into one stream.

Now by default iniread will stop at first file; old behavior can be
restored by -j|--join switch.