fix: parse boolean properties case-insensitively

[fallintoplace]

Summary

• parse boolean table and catalog properties case-insensitively, matching Java's Boolean.parseBoolean
• continue treating values other than a case-insensitive true as false
• add coverage for lowercase, uppercase, mixed-case, false, and unrecognized values

Testing

• util_test --gtest_filter=ConfigTest.ParseBooleanIgnoringCase
• pre-commit hooks for the changed files

[evindj]

pretty sure you did but it would ne nice to check for other places in the code base where similar comparison with literals is made.

[fallintoplace]

Good call. I found the same case-sensitive parsing in the S3 properties and pushed a follow-up for s3.ssl.enabled and s3.path-style-access. The other literal comparisons I found are Avro schema attributes rather than configuration properties, so I left those unchanged.