As shown in the tests, that type has the flexibility of being able to be
cast to from any other numeric type. This gives us flexibility without
bloating the API with lots of type-specific functions.
The client functions to make configuration changes are not publicly available
(require a super user) and they have username, orgname parameters like the
server-sixe functions
The difference between
```
=> select * from cdb_service_quota_info();
service | monthly_quota | used_quota | soft_limit | provider
----------------+---------------+------------+------------+------------------
isolines | 1000 | 0 | f | heremaps
hires_geocoder | 5 | 2 | f | mapzen
routing | 1500000 | 0 | f | mapzen
observatory | 1000 | 0 | f | data observatory
(4 rows)
```
and
```
=> select cdb_service_quota_info();
cdb_service_quota_info
-------------------------------------------
(isolines,1000,0,f,heremaps)
(hires_geocoder,5,2,f,mapzen)
(routing,1500000,0,f,mapzen)
(observatory,1000,0,f,"data observatory")
(4 rows)
```
is important to pl/proxy. In the later case, rows only have one field
(a tuple) and it complains with "Got too few fields from remote end".
Add config function in postgres explicitly to get MapzenGeocoderConfig.
Bump versions for client and server APIs. New MapzenGeocoderConfig
included to be able to use current QuotaServices with non-configured
users.
Add routing with waypoints functions to client and server. Includes
signature checks tests for the Postgresql functions and unit and
integration tests for the Python library.
Add client v0.6.0 and server v0.9.0
