Allow case insensitive bools and move to numeric render

[zlonast]

The .cabal file parser now accepts boolean values in a case‑insensitive manner (true, True, TRUE, false, etc.) without emitting a warning.
Previously only True and False were treated as “standard”, and other capitalisations triggered a parse warning. That warning was introduced in 2008 as a backwards‑compatibility shim to prevent Hackage uploads that would break very old Cabal versions. Since all supported Cabal releases can now handle case‑insensitive booleans, the warning has been removed as unnecessary.

Additionally, the rendering of certain boolean‑like flags has been changed to use numeric levels:

• For the -O (optimisation) flag, True or an unspecified value now renders as -O1, while False renders as -O0.
• For the -g (debug info) flag, True or an unspecified value now renders -g2, while False renders as -g0.
  This makes the displayed compiler flags more consistent with their internal semantics (e.g. optimisation level 1 is the default).

origin commit in 2008: e92d6573#r185301031

research done by @jappeace: https://github.com/haskell/cabal/pull/11716/changes#r3243914138

Template B: This PR does not modify behaviour or interface

E.g. the PR only touches documentation or tests, does refactorings, etc.

Include the following checklist in your PR:

• Patches conform to the coding conventions.
• Is this a PR that fixes CI? If so, it will need to be backported to older cabal release branches (ask maintainers for directions).

[zlonast]

@philderbeast You often make pull requests like this, I'm interested in your opinion on this matter.

[tdammers]

LGTM; comments are not show stoppers, just things I think would be worth considering.

[zlonast]

@tdammers thanks for your feedback!