haddock-project: add CommonSetupFlags

[9999years]

Split off of #10292. This lets cabal haddock-project use the standard CommonFlags that other commands use to set verbosity and so on.

• Patches conform to the coding conventions.
• Any changes that could be relevant to users have been recorded in the changelog.
• The documentation has been updated, if necessary.
• Manual QA notes have been included.
• Tests have been added. (Ask for help if you don’t know how to write them! Ask for an exemption if tests are too complex for too little coverage!)

[geekosaur]

Note: API change, can't be backported.

[mpickering]

I am not sure this is the right direction of travel -- why are we propagating the design flaw of reusing the options parsers for the ./Setup interface for the cabal-install interface?

[9999years]

I am not sure this is the right direction of travel -- why are we propagating the design flaw of reusing the options parsers for the ./Setup interface for the cabal-install interface?

I can't comment on the design here, but all the other cabal-install commands use this pattern.

[Kleidukos]

@coot ping

[ulysses4ever]

Note: API change, can't be backported.

Maybe we should have a label for this case...

[ulysses4ever]

why are we propagating the design flaw

This PR is not the best time and place to discuss such a big, long-standing issue. I'd prefer this be merged and have the issue discussed separately. But I rarely touch Cabal (as opposed to cabal-install), so maybe I'm wrong.

[gbaz]

I agree we should eventually reconsider flag design, but this is not the place. For now let's proceed with the way things are, and it would be good to file an issue for a future refactor.

[coot]

LGTM

[9999years]

Rebased for mergify permissions

[geekosaur]

@9999years , you need to rebase again; see #10445.