• I agree to follow the project's code of conduct.
• I added an entry to CHANGES.md if knowledge of this change could be valuable to users.

Fixes #831 - an ergonomics issue.

So you can now:

- use geo_types::{Coordinate, Point, Line, LineString, Polygon, MultiPoint, MultiLineString, MultiPolygon, Rect, Triangle, Geometry, GeometryCollection};
+ use geo_types::geometry::*

And similarly with geo:

- use geo::{Coordinate, Point, Line, LineString, Polygon, MultiPoint, MultiLineString, MultiPolygon, Rect, Triangle, Geometry, GeometryCollection};
+ use geo::geometry::*

(quoting from #831):

In general, I'm not a fan of large wild card imports because later in the code it's hard to know where something came from, but for cases like this when it's a small number of well known things, I think it's helpful with little downside.

Note that I diverged slightly from my original plan in #831.

I initially sought to introduce a new geometries module, but then I was afraid it'd be too confusing to have both a geometry and a geometries module, so opted instead to have a geometry module which, as well as defining the Geometry enum, also re-exports the inner variants.