#58 Follow GNU Conventions on Command Line Arguments

[Elizabeth F]

See here for GNU conventions on command line interfaces:

https://www.gnu.org/prep/standards/html_node/Command_002dLine-Interfaces.html

Issues to be resolved, based on this:
1. All "long" options should start with '--': --robust, --max-timeout-duration, --skip, --xml, --name, etc. Having some long options start with '-' and some with '--' is unnecessarily confusing.
2. Add a --version option

$ landice/tests --help
EVERYTRACE REFERENCE "/home2/rpfische/exp/160623-stieglitz/pkgs/18635298f1893ce3e8b9e362f1f02473/lib/libmodele.so" 0x7fde7d15e680
Command line arguments:

Options:
'-h', '--help' : Prints this message
'-v', '--verbose' : Logs start/stop of each test
'-d', '--debug' : Logs start/stop of each test (same as -v)
'-o <file>' : Diverts output to specified file
'-robust' : (experimental) runs tests in a separate shell
Attempts to detect/handle hangs and crashes
'-max-timeout-duration <duration>' : Limit detection time for robust
'-max-launch-duration <duration>' : Limit detection time for robust
'-skip n' : used by remote start with 'robust' internally
This flag should NOT be used directly by users.
'-xml <file>' : output JUnit XML to specified file
XML can be used with e.g. Jenkins.
'-name <name>' : give tests an identifying name in XML output</name></file></duration></duration></file>

..
Time: 0.000 seconds

OK
(2 tests)