Reorganize generated documentation

[mlipper]

The geoclient-service module uses the geoclient-doc.xml configuration file in the geoclient-core subproject to provide dynamically rendered HTML-based documentation at runtime. This is both unnecessary and error-prone.

Originally, the Geoclient XML metadata was created by parsing Geosupport's Universal Programming Guide PDF document to produce a "base" set of field definitions for the data elements returned by the various Geoclient endpoints (address, bbl, etc.) by mapping the endpoints to their proxy targets (Geosupport functions) using the UPG's data dictionary.

Due to variance in the PDF's (which were not intended for this kind of reverse-engineering) and the use of "tech bulletins" by DCP to announce new release changes, this "automated" integration quickly became a manual process resulting neglect and inclomplete/out-of-date generated HTML.

DCP has recently communicated its intention to place this documentation content online as part of their GOAT application. As such, Geoclient should simply link returned data fields on a per-endpoint basis to the appropriate section of GOAT and get rid of the convoluted code for assembling this info using XStream.