Register routes for publish intents

In order to be able to serve 404 or placeholder pages with appropriate cache headers, the requests need to be routed to a frontend app that can query the content store.

This makes publish intents require a set of routes.  If the intent has a corresponding content item, only the set of routes that don't already exist for the item are registered.  Otherwise all the intent's routes are registered.