Avoid name collision with macros TRUE and FALSE.

[1uc]

See #721.

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (master@2759770). Click here to learn what that means.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##             master     #722   +/-   ##
=========================================
  Coverage          ?   82.42%           
=========================================
  Files             ?       67           
  Lines             ?     4513           
  Branches          ?        0           
=========================================
  Hits              ?     3720           
  Misses            ?      793           
  Partials          ?        0           

Impacted Files	Coverage Δ
include/highfive/bits/H5Converter_misc.hpp	85.84% <ø> (ø)
include/highfive/bits/H5DataType_misc.hpp	78.64% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[1uc]

While details::Boolean::HighFiveFalse seems excessive, False looks to much like the Python name for true. We're free to rename it as it's not part of the API, so the only concern is to avoid macros interfering.