Replace boolean value of config variables to literal string when showing to the user

[imrraaj]

This pull request fixes following issue

• Show literal "true"/"false" when reading boolean values instead of an empty string #165

I refactored the code to return the string representation of a boolean value (i.e., 'true' or 'false'), which is easier to display to the user. Previously, when the variable's value was true, it would render as '1', and blank when false. Using strings allows us to provide clearer guidance to the user regarding which value is true and which is false.

[imrraaj]

Can I get a review on this PR? @danielbachhuber

[pwtyler]

@imrraaj, can this be tested with the behat feature tests to cover the various types of truthy/falsy values that might be used in wp-config?

[schlessera]

@imrraaj I think this can potentially break scripts that already rely on the current behavior.

We could put this behind a flag and have the flag default to using this if interactive and not using this if non-interactive.

I'll need to check what prior behavior we have that is similar to this so we can stay consistent...

[codecov]

Codecov Report

❌ Patch coverage is 83.33333% with 1 line in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
src/Config_Command.php	83.33%	1 Missing ⚠️

📢 Thoughts on this report? Let us know!

[swissspidy]

Related: wp-cli/wp-cli#6162 / wp-cli/wp-cli#5542