Option naming should be more consistent

[sjakobi]

Motivated by this SO question I just updated the documentation for the build options.

Here are a few inconsistencies that I noticed:

• In the yaml config we have test-arguments, haddock-arguments but benchmark-opts.

• We have test and test-X, haddock and haddock-X, but bench and benchmark-X.

• • --test-arguments -> test-arguments: additional-args
  • --haddock-arguments -> haddock-arguments: haddock-args
  • --benchmark-arguments -> benchmark-opts: benchmark-arguments

• haddock-deps, open-haddocks and haddock-internal should be inside the haddock-arguments block

• test additional-args and haddock-arguments each take a list of strings, while benchmark-arguments takes a single string (I didn't check the CLI)

[borsboom]

Related (possibly duplicate?): #652

[ruuda]

Another one that I just ran into: we have --ghc-options to pass arguments to GHC, but --{test,haddock,benchmark}-arguments.