Put the default fields for the city database in the same order as the
valid fields for the city database. Interestingly, the 'TIMEZONE' (and
the 'IP') are the only valid non-default properties.

Rather, they're the object properties under which those values will be
written within a containing 'location' object, if the 'location'
property has been selected.

and use a more general term instead. Maxmind seems to consistently
refer to the GeoLite2 databases as 'GeoLite2 databases' and to their
commercial offerings as 'GeoIP2 databases' -- both of them are 'IP
geolocation databases' (which appears to me to be a generic term that
applies to both their free and commercial databases as well as the
things that others in the industry might provide).

nor are any 'included in the module'.