Consistent CLI parameter naming and improvement

[vinjana]

Currently, calling Roddy is unintuitive. There is parameters starting with and without 'use', parameters with camel-case or in all lowercase. Parameters names are very long. There is short parameters ("c", "v") that need double dash prefix, which is not the convention in unix. Also parameters with arguments always need a equality sign.

Come up with a parameter scheme that

• follows Unix conventions. Single letter parameters must always have a single dash.
• come up with a very clear set of short parameter names
• allow parameter arguments with and without equality signs

Preferentially use some parameter parsing library that enforces clear rules and may already suuports long and short parameter variants.

Decide on the eventual rules and in the future reject all PRs that don't follow these rules!

[vinjana]

Some code for stripping off all "use" prefixes, and making parameters case insensitive was implemented in the Roddy JVM code in https://github.com/TheRoddyWMS/Roddy/pull/373.

A further implementation failed (or was postponed) because the roddy.sh startup-script (and all the mess behind it) was too much of a hassle. We first need to implement #376 .