Manage Google API error codes

Google has now changed their geo-coding API. See https://googlegeodevelopers.blogspot.com/2016/11/address-geocoding-in-google-maps-apis.html for more details.

The Geocoding API is now much more sensitive to having exact addresses, and will return ZERO RESULTS if the address does not exactly match. This code is not managed in CiviCRM, leading to blank geographic coordinates in the address.

We should instead default to the Places API, which accepts fuzzy addresses, as a second method to geocode the address. The calling parameters and returned structured are very similar in both APIs, and the same API key can be used for both APIs, so that second query is trivial.

I do not know how this influences the daily quotas and/or billing, so we might make insert an additional setting to opt-in this second API call.

I have had many addresses that failed to resolve with the Geocoding API and did with the Places API. This is especially true for event locations, for which the address is often incomplete and/or ambiguous.

https://developers.google.com/places/web-service/search