Rename distance* functions to greatCircleDistance*

[nrabinowitz]

Per offline discussion: The intent of this change is to disambiguate the point-to-point distance functions from the grid distance functions, particularly in binding contexts where the unit suffix may be lost.

This was just a straight search-and-replace, no other code changes.

[coveralls]

Coverage increased (+0.0004%) to 98.66% when pulling 57ac6c7 on nrabinowitz:lat-lng-distance into 1e661dc on uber:master.

[isaacbrodsky]

Please update the docs - API docs, upgrade instructions, and CHANGELOG.

[nrabinowitz]

Done, thanks. When upgrading the docs I assumed that JS and Java would use latLngDistance and Python would use latlng_distance.

[ajfriend]

Sorry, I'm waffling on this, but I'm currently leaning toward haversineDistance, even if that might refer to a specific formula. I think it's less ambiguous than LatLng and seems to be generally accepted as the right name for this sort of thing:

• https://scikit-learn.org/stable/modules/generated/sklearn.metrics.pairwise.haversine_distances.html#sklearn-metrics-pairwise-haversine-distances
• https://pypi.org/project/haversine/
• https://docs.snowflake.com/en/sql-reference/functions/haversine.html

Too late to consider this version?

[ajfriend]

I guess "haversine" isn't used in the the OGC names. Its STDistance: https://docs.microsoft.com/en-us/previous-versions/sql/sql-server-2008/bb933808(v=sql.100)

...but i don't think we're considering calling it STDistance here :)