Regarding Issue #18

performSearch_GenerateResults_OSTPoints() and performSearch_GenerateResults_Trails() now explicitly tag the results with their datatype: ostpoint or trail
This allows some later examiner of the results to determine their data type.

Used this new "result datatype tagging" to improve performSearchReally() to explicitly use this (and future datatypes) rather than relying on result.geometry.paths=='undefined'

performSearchReally() also now adds a .map_feature attribute to the results listing, so a result can be positively linked to a specific feature on the map (e.g. a MultiPolyline or a Marker)

Added the tap handler to the Results listview: handleSearchResultTap() which hands off to OSTPoint and Trail sub-handlers. These switch to the map, zoom in, and trigger the side panel.