fix(Cabal): Accept boolean values for debug-info and optimization levels

[zlonast]

fix: #12140

debug-info: False ​​are treated as NoDebugInfo, and debug-info: True ​​are treated as NormalDebugInfo

---

Template Α: This PR modifies behaviour or interface

Include the following checklist in your PR:

• Patches conform to the coding conventions.
• Any changes that could be relevant to users have been recorded in the changelog.
  • Is the change significant? If so, remember to add significance: significant in the changelog file.
• 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!)

[philderbeast]

If we're parsing booleans for debug-info in the project, would that also apply to the command line? If not, is error the best message?

$ cabal build --help
...
--enable-debug-info[=n]        Emit debug info (n is 0--3, default is 0)
--disable-debug-info           Don't emit debug info

$ cabal run cabal-install:exe:cabal -- build all --dry-run \
   --enable-debug-info=True
...
Can't parse debug info level True

HasCallStack backtrace:
  error, called at src/Distribution/Simple/Compiler.hs:383:8 in
  Cabal-3.19.0.0-inplace:Distribution.Simple.Compiler

$ cabal-3.18.1.0 build all --dry-run --enable-debug-info=True
Can't parse debug info level True
CallStack (from HasCallStack):
  error, called at src/Distribution/Simple/Compiler.hs:392:8 in
  Cabal-3.18.1.0-inplace:Distribution.Simple.Compiler

[zlonast]

@philderbeast Thanks for such a detailed review, yes, I think this approach should be applied to the command line as well.