Report URL type errors as HTML responses

Currently type errors in URLs are reported in the application log, but not the HTML response. The response should include both a list of all the type errors and documentation for the most likely route or routes that the URL was intended to be.

Depends on https://github.com/EspressoSystems/tide-disco/issues/17

Start by reviewing the dependency in issue #17, then trace where URL type errors are currently reported in the application log. Done means the HTML response includes all type errors and documentation for the most likely intended route or routes.

Written by the indexing model from the issue text.