Fix: handle valueless boolean CLI flags at compile time

[kickster97]

WHAT is this pull request doing?

Valueless boolean CLI flags like --clustering and --raise-gc-warn are broken. OptionParser passes an empty string for flags without =VALUE, and parse_value("", Bool) evaluates to false instead of true.

Fixed by detecting valueless boolean flags at compile time in the parse_cli macro and assigning the correct literal (true, or false for --no- prefixed flags) instead of always going through parse_value.

maybe this code is a bit clunky? I'd love to discuss if there are more elegant solutions

HOW can this pull request be tested?

run updated specs

[spuun]

Try

      @[CliOpt("", "--clustering", "Enable clustering", ->(String) { true }, section: "clustering")]

[claude]

No issues found.

The fix correctly uses explicit Proc value parsers for the three valueless boolean CLI flags (--no-data-dir-lock, --raise-gc-warn, --clustering). The approach is sound: when OptionParser passes an empty string for valueless flags, the lambda returns the correct literal value instead of going through parse_value("", Bool) which would evaluate to false. Specs cover the new behavior.

[kickster97]

Try

      @[CliOpt("", "--clustering", "Enable clustering", ->(String) { true }, section: "clustering")]

Think that makes for a better solution!