CeylonRunTool should not try to interpret command arguments

[CeylonMigrationBot]

[@quintesse] The current run tool doesn't permit the following:

ceylon run --verbose org.codejive.ceylon.httpd/1.0.2 --port 8080

That's pretty bad and I think we should fix this for M4.
(Sorry Stef ;)

[Migrated from ceylon/ceylon-runtime#26]

[CeylonMigrationBot]

[@quintesse] I see that you can fix this by inserting -- before the module name, but I don't think that for "run" this should be necessary. But at least this means we can probably downgrade this from "high prio" and "M4".

[CeylonMigrationBot]

[@FroMage] Aw maaaan.....

[CeylonMigrationBot]

[@FroMage] M6.

[CeylonMigrationBot]

[@quintesse] This should now be fixed.... mostly.... the example uses --verbose which is exactly the only option that is hard-coded in the Launcher, at a point where we don't actually know anything about the tool we're running.

[CeylonMigrationBot]

[@quintesse] I'm taking a break from this, I'm going to have to discuss with @tombentley how to proceed on this because the amount of work involved for the gain it gets us is way out of proportion.

The --verbose option is now handled at least (and generically by all our tools), what remains is --help which is what is causing the headaches.

NB: there is another hard-coded option that has to be handled so early in the startup that the tool chain can't be involved yet (a chicken and egg problem): --sysrep. Right now I see no way that a user program could use that option without resorting to the use of the -- fence argument. Hopefully there won't be much user programs that want to use the --sysrep option themselves.

[CeylonMigrationBot]

[@FroMage] Moving to 1.2, unfortunately.