Add support for Pointp.in ip geolocation

Allow lookup service to fully opt-out of https

If you have an address geocoding service that you want to use HTTPS with
and then attempt to use an ip_geocoder that does not support HTTPS (e.g.
Telize) then the ip_geocoder lookups will fail because
Geocoder::Lookups::Base#make_api_request turns on opts[:use_ssl] based
on that single configuration value.

Rather than allowing for per-provider HTTPS configuration I have just
refactored Geocoder::Lookups::Base call a private `use_ssl?` method
which can be overridden by individual lookup provider implementations.
The default implementation of `use_ssl?` simply returns the value from
the config thus preserving the existing behavior but this allows
subclasses, like Telize, to override `use_ssl?` completely to return
false and thus fully opt-out of HTTPS regardless of what the
configuration was.

json coming from geocodio has changed from floats to strings

Fix CHANGELOG.md formatting

This fix adds formatting to match the other version headers.  They were previously plain text.

Date typo in changelog

Fix Bing reverse geocode lookups

Update README.md

Bump up Ruby version for Travis to 2.1.2

Switch to byebug for MRI 2.x debugging.

Switch to byebug for MRI 2.x debugging.  Debugger is not supported for 2.1.2 and up, and was never fully 2.x compatible.

Use correct fixtures in tests and make required changes so tests pass.

Response to GH issues #579 and #663.

Updated MaxMind Local setup instructions

use more forgiving 'unstructured' query format in Bing Locations API

See docs: http://msdn.microsoft.com/en-us/library/ff701711.aspx

See: http://docs.travis-ci.com/user/languages/ruby/

allow to pass in language/locale parameter on per request base