logging/printing arguments harness started with

Often javatest is started not directly but via a separate tool, script, framework. For example: jck4jdk, qatools, aurora, qagrid, etc.
The tool may have different set of options that non-trivially translated to
javatest's options which are invisible (i.e. no way to see how exactly javatest is invoked).
This request is to provide ability for javatest invoked from inside some tool
to print arguments that are passed to javatest.

For example, printing argument can be triggered by a property:
-Djavatest.verbose=args
or something like that.