[Server] Change loopback to observatory just to call the observatory extension functions

• Change how the blue/green system is working in the server side. Now the loopback is only in the observatory extension functions call instead in all the dataservices-api function for observatory

Blue/Green deploy for observatory functions

Added Blue/Green capability to the data observatory functions in order to be able to use staging or production databases

[Server] Change data observatory quota check system

• Use redis based config if exists, if not use the db config value
• Refactor key to segregate more, now the services is called obs_snapshot

[Server] Data observatory integration

• Added obs_get_demography_snapshot function
• Added obs_get_segment snapshot function
• Integrated quota checking

[Client] Data observatory integration

• Remove old versioning system for client side
• Added obs_get_demography_snapshot function
• Added obs_get_segment snapshot function
• Integrated quota checking

[Server] Mapzen routing and geocoder quota check

Add Mapzen routing and geocoder quota check

[Server] Agnostic geocoder

• Now the implementation knows how to get the iso3 for the passed country in order to pass it to Mapzen
• The city an the state/province parameters are used for mapzen too

[Server] Isoline credentials independent from geocoder

• Use specific isoline routing credentials for a provider for isoline functions, which were previously using the general credentials from the provider.

[Server] Mapzen geocoder integration

• Integrated Mapzen geocoder for street level geocoding function

[Server] Routing function improvements

• Deleted old versioning system
• 4xx responses returns empty routes despite to raise an exception
• In some cases we return and empty response: one of the inputs is null, there is no generated shape for the route, etc