Make String to Boolean parameter conversion more strict

[s-rwe]

Cause use of anything other than 'true' or 'false' (case-insensitive) fail in conversion, to make potential typos explicitly visible (instead of implicitly just treating all else as 'false')

Includes a few tests for failures on invalid values, for conversions handled by StringToBooleanAndCharPrimitiveConverter.

Issue: #3177

---

I hereby agree to the terms of the JUnit Contributor License Agreement.

---

Definition of Done

• There are no TODOs left in the code
• Method preconditions are checked and documented in the method's Javadoc
• Coding conventions (e.g. for logging) have been followed
• Change is covered by automated tests including corner cases, errors, and exception handling
• Public API has Javadoc and @API annotations
• Change is documented in the User Guide and Release Notes

[sbrannen]

Thanks for submitting the PR so quickly!

I requested a few minor changes.

[s-rwe]

Thanks for submitting the PR so quickly!

I requested a few minor changes.

Sure thing, likewise thanks for the quick review :)

Requested changes pushed accordingly.

[sbrannen]

The proposal looks good to me from a technical standpoint.

All that's missing is an entry in the release notes and, potentially, a note in the user guide.

Though I think we should hold off on those last two tasks until the rest of the team has voiced their approval.

[marcphilipp]

Team Decision: Make it more strict by default since it's a more sane behavior.

[marcphilipp]

@s-rwe Could you please add an entry to the release notes and update the table in the User Guide?

[s-rwe]

@s-rwe Could you please add an entry to the release notes and update the table in the User Guide?

Ok sure thanks, done accordingly.

[marcphilipp]

I'll take it from here.

[marcphilipp]

@s-rwe Thank you for you contribution! 🙇‍♂️