Minor comment touchups
selectSeason_RenderMapContent() changed behavior for OST Points which have an invalid/blank Type. Previously they were silently skipped, but now this throws an exception. If we allow an OST Point not to draw on the map, then we can have a search result which has no corresponding marker -- and that means no distance calculation, no tap-info, etc. and creates failures later (e.g. a search for All Amenities, was the test case which found Richmond Ridge with a blank Type)

sortAndRenderSearchResults() no longer performs the calculation of the latlng for each point. This is now done by performSearchReally() as the results are loaded into $('#results_list').data('results')  The tradeoff is that this is a one-time calculation of the point: faster performance and lighter on battery consumption, but means that as you move it won't repeatedly find THE CLOSEST point for trails. This shouldn't be a realistic issue, though, unless someone drives to the wrong end of a long trail based on outdated search results.