- Fixes #1353
  - Do not limit the results returned from Pelias to 1;
  - Removed test that was enforcing this condition;

It appears that at some point they changed the "TLS only for paying
customers" rule.

See: https://ipinfo.io/developers#https-ssl
"Our API is available over a secure HTTPS connection for all users, even
on the free plan."

Defunct as of Feb 1, 2018: https://mapzen.com/blog/shutdown/

Fixes #1059.

Make Nominatim the default lookup and map provider.

Closes #1026.

Appears to be defunct.

Fixes #609. Bing seems to support this type of character escaping now.
It's not discussed in their documentation but it works with every query
I've tried so hopefully we're finally good on this issue.

Also remove some unnecessary assertions from tests.

No longer seems to exist.

Fixes #1299.

* Update initializer template to use ipinfo_io

* Implement ipstack lookup

* Add Ipstack readme documentation

* Add post-install message

* Remove DSL from ipstack lookup

* Remove unnecessary logging

* Update post-install message

Freegeoip/IPstack no longer provides keyless service.

some google geocoding requests have bounds within the result.  add a
helper to extract these.

* Add tests to cover results with no bounds

In this case, calling .bounds should return nil.  Oddly, calling
viewport on a result with no viewport causes the current code to `fail`.
I have preserved this behavior even though I think it to be a little
odd.

but default to HTTPS (custom hosts may not support HTTPS).
This partially reverts 7cb0acc9.

This reverts commit 385aafa0.

Should have been part of 7cb0acc9

See https://github.com/ruby/ruby/commit/e1b432754553423008a14d39d0901eabc99e7ddb

see: https://github.com/alexreisner/geocoder/pull/1254#issuecomment-359118927

Bing returns the status codes within the json response. When a request is
forbidden, it will return a 403. If there is an internal server error,
it will return a 500. And if the service is unavailable for some other
reason, it will return a 503. That information was obtained from bing's
[Status Codes and Error
Handling](https://msdn.microsoft.com/en-us/library/ff701703.aspx)
documentation.

We handle those three status codes here to raise
`Geocoder::RequestDenied` (for 403) and `Geocoder::ServiceUnavailable`
(for 500 and 503). This allows for the users of the Geocoder to handle
those errors in their applications.

Remove silly check for HTML tags
Add test case for invalid json