Issue nwbib 17 spatial 99

See hbz/nwbib#17.

While transforming the hbz01 the literal of the location field of `spatial#99` is passed to the piped morph `morph-nwbibhbz01-buildGeoOsmUrl` which looks if the literal is already stored in a SQL DB and otherwise builds the nominatim url. This url is opened and the result is decoded with the newly JSON(P) decoder to gain the latitude, longitude and the OSM ID. The result is passed via a tee to :

1. the morph-osmResult-buildGeonamesLatLonUrl which builds the URL to lookup geonames. The result is parsed via morph-jsonGeonames2mysqlRow and stored in a MySQL DB (hence the MysqlWriter).

2. the morph-jsonOsm2mysqlRow builds the data to bes tored in MySQL DB to enable concordance between the nwbib literals and OSM related links.

See the flux for detailed workflow.