"datetimes()" now accepts timezone-aware "min_value" and "max_value"
bounds, which are treated as moments in time. In this case "timezones"
defaults to "timezones()", and each generated datetime lies between
the two moments. Passing one aware and one naive bound is an error.
If annotated-types has been imported, the overloaded type hints for
this strategy now distinguish naive from aware datetimes using
"Timezone" metadata.
The canonical version of these notes (with links) is on readthedocs.