"Heavy-duty" configurable `geocode` command

[jqnatividad]

qsv bundles reverse-geocoder - a "lightweight" static, nearest city geonames geocoder.

But for real, street-level geocoding, we need a configurable geocoder that can use the user's geocoder backend of choice.

For the initial implementation of a heavy-weight geocoder, we'll start in order of implementation:

• pelias (because it's open-source, and users can stand up their own customizable pelias geocoder instance; no ToS prohibiting caching results, etc.)
• google geocoder

Other geocoder backends in the backlog:

• US Census
• ArcGIS World Geocoder (as most jurisdictions have a subscription)

This geocoder will be its own qsv command - geocode unlike the current lightweight one, which is just one of many apply operations.

[jqnatividad]

this will be a specialized version of the fetch command (#77).

[jqnatividad]

Since qsv will be presented at NYC Open Data Week (Mar 5-12 2022), the first integration target will be NYC's geocoder geoclient.

[jqnatividad]

Now that fetch is largely done and has Redis response caching, we can build on fetch to implement this.

[github-actions[bot]]

Stale issue message

[jqnatividad]

Reopening now that fetch has stabilized.

Also, move the geonames geocoder from apply to this command as the default geocoder.

[github-actions[bot]]

Stale issue message

[jqnatividad]

Initial installment done using updateable geonames database with https://github.com/jqnatividad/qsv/pull/1231