Improve address scoring in `latlng_to_address()`

[nexushoratio]

Improve address scoring in `latlng_to_address()`

[nexushoratio]

Sampling some places demonstrates that it is NOT straightforward in any way. For some, the plus_code was the best, others, premise, others street_address.

Each result also has a ['geometry']['location'] associate with it. Maybe picking the one that is closest to the original latlng is best? Or maybe the results array is already sorted and the best is the first element (though I was unable to find any documentation on this)?

Anyway, the only place that uses this information is when we generate a KML file for the optimal route, and we are unable to do that right now anyway because the old libraries no long exist.

Figuring out if closest result is best would currently depend on pyproj anyway, and that might go away with #14 .

So, this is a pretty low priority item at the moment.