Change H3Poly/H3MultiPoly to LatLngPoly/LatLngMultiPoly

[ajfriend]

Lat/Lng vs Lng/Lat order is one of the biggest sources for user bugs/questions/issues, especially when creating Polygon and MultiPolygon objects. Lng/Lat order is what's used in many other tools like geopandas and GeoJSON, but the H3 C library uses Lat/Lng order.

h3-py will stick with Lat/Lng order, but we can alleviate the mistakes caused from switching orders between tools by potentially making the ordering explicit in the name. An additional goal is to make it obvious that our polygon and multipolygon objects are different from shapely Polygon and MultiPolygon objects.

Some options:

1. H3Poly and H3MultiPoly (current; users need to read docstrings to know/recall ordering)
2. LatLngPoly and LatLngMultiPoly (explicit, but a bit long)
3. constructors like H3Poly(outer, *holes, latlng=True) (short name, "latlng choice" more prominent in the constructor signature than docstring)

I'm leaning towards LatLngPoly and LatLngMultiPoly but wanted to have a separate discussion here for future reference rather than having it hidden in the comments of #301.

I see it as a decision of how forcefully we want to remind the user of the ordering. In ordering of increasing forcefulness:

1. documentation or function docstrings
2. constructor signature
3. class name