Automate the creation of the test-suite driver

[rouson]

With the new driver structure introduced in PR #86, it's likely that straightforward source analysis could be used to generate the drier program automatically in a manner similar to the Veggies companion Cart. Referring to Julienne's test suite as an example, write a program that does the following:

1. Find all modules in the test suite that contain a non-abstract derived type that extends Julienne's test_t type.
2. Create a driver program containing one use statement for each such module and one corresponding only clause for each test_t child type.
3. Add a use julienne_m, only : test_harness_t, test_fixture_t statement.
4. Invoke the test_harness_t user-defined structure constructor with an actual argument that is an array of elements defined by invoking the test_fixture_t user-defined structure constructor.
5. Pass each test_t child type's structure constructor as the lone argument to each invocation of the test_fixture_t user-defined structure constructor.
6. Call the report_results type-bound subroutine on the constructed test_harness_t object.

[rouson]

PR #92 achieves a similar level of automation at the cost requiring a very simple JSON file naming the test subjects.