OAR commands usage enforcement

[bpichot]

Case 1: Junk arguments in oarsub command cause reservations to be terminated as they start

See Grid'5000's bugzilla: https://intranet.grid5000.fr/bugzilla/show_bug.cgi?id=7931
I didn't test with other versions than 2.5.8-rc3, which is in production on Grid'5000.

These two commands for instance schedule reservations that go from Waiting state to Lauching and immediately Finishing:

oarsub -r "2017-3-17 17:19:0" hello world
oarsub junk -l nodes=1,walltime=1 junk -r "2017-3-17 17:21:0" junk

Passive jobs print oarsub usage help in such a case, for instance with:

oarsub junk -l nodes=1,walltime=1 sleep 1d

Interactive jobs are tolerant to junk arguments, for instance this command will launch a valid job:

oarsub junk -l nodes=1,walltime=1 junk -I junk

[npf]

Case 2: oarnodes -l --sql "..." returns all nodes

https://intranet.grid5000.fr/bugzilla/show_bug.cgi?id=7969