Make static asset prefixes more explicit

[jacksontj]

Right now the base handler checks for anything to exist as a static asset before doing dynamic pages. This would mean that if we where to put a file such as web_site_page in the directory (./web/limitless5) then the page goes missing.

Mappings of prefix -> static assets should be done either (1) in config or (2) in database

[zelin-l]

@ghowland We could do something like the web_widget table where we load all of the html of web_widgets into the db and also store the relative path.

We could create a table called web_site_page_static where we load all of the html of static pages into a table like web_site_page_static and store both the html & static path. Then when we check for a static asset, instead of doing a specified relative directory, we would just do a search in the table like dynamic web pages.

web_site_page_static would include fields like: _id, name, path, info, html, (maybe udn_data_json)