Fix custom boolean option labels using oneOf schemas

[pushred]

Reasons for making this change

As previously reported in the following issues specifying boolean options with a oneOf schema does not work as expected.

• Fixes Support oneOf syntax in BooleanField with radio widget. #945 - Support oneOf syntax in BooleanField with radio widget.
• Fixes oneOf{const,title} with boolean type properties causes titles to be displayed in lower case #781 - oneOf{const,title} with boolean type properties causes titles to be displayed in lower case
• Fixes oneOf{const,title} reorders boolean options unlike enum/enumNames #782 - oneOf{const,title} reorders boolean options unlike enum/enumNames

These issues all essentially result from a lack of support for oneOf in BooleanWidget altogether. This implements that support with a similar approach to the optionsList utility.

I've also added the ability to override true/false ordering for boolean options by defining a custom enum: [false, true] pair. This is entirely separate of oneOf but it makes behavior consistent between the two schema options.

Checklist

• I'm updating documentation
  • I've checked the rendering of the Markdown text I've added
  • If I'm adding a new section, I've updated the Table of Content
• I'm adding or updating code
  • I've added and/or updated tests
  • I've updated docs if needed
  • I've run npm run cs-format on my branch to conform my code to prettier coding style
• I'm adding a new feature
  • I've updated the playground with an example use of the feature

[epicfaace]

Merged, thanks @pushred !