Don't mangle existing template routes.

[smashwilson]

v3 seems to have broken the client's ability to render already-mapped content in getting unmapped content to work. Basically, the control repository's routes.json file was being mangled during service pod launch:

$ jq . < ~/.deconst/control-0/routes.json 
{
  "developer.rackspace.com": {
    "routes": {
      "developer.rackspace.com": {
        "routes": {
          "^/": "default.html",
          "^/$": "index.html",
          "^/signup": "index.html",
          "^/databases": "databases-index.html",
          "^/blog": "blog-index.html",
          "^/blog/.+?": "blog-single.html",
          "^/blog/page?": "blog-index.html",
          "^/blog/categories": "blog-index.html",
          "^/blog/authors": "blog-index.html",
          "^/docs": "docs-home.html",
          "^/docs/.+?": "docs-page.html",
          "^/docs/user-guides/infrastructure/": "user-guide.html",
          "^/docs/cloud-images/v2/developer-guide": "docs-singlepage.html",
          "^/docs/cloud-load-balancers/v1/developer-guide": "docs-singlepage.html",
          "^/docs/rack-cli/": "rack-cli.html",
          "^/sdks": "sdks-home.html",
          "^/sdks/.+?": "sdks-page.html",
          "\\.xml$": "feed.xml"
        }
      }
    }
  }
}

This change handles the routes structure consistently and renders content with the correct template either way.

Fixes deconst/deconst-docs#170.