Maintain existing path, but add view and uniqueKey to RouteData

There's a good argument for relaying the discovered topic's `UniqueKey()` as a `RouteVariable`. But rewriting the `path` variable, as was previously done, not only confused terms, but also breaks the processing if/when `TopicsRouteHandler` is reevaluated.

Author: JeremyCaney

Ignia.Topics.Web/TopicsRouteHandler.cs

@@ -99,10 +99,11 @@ public IHttpHandler GetHttpHandler(RequestContext requestContext) {
       /*------------------------------------------------------------------------------------------------------------------------
       | Set route data
       \-----------------------------------------------------------------------------------------------------------------------*/
+      routeData.Values          ["view"]                        = viewName;
       routeData.Values          ["targetPath"]                  = targetPath;
       routeData.Values          ["contentType"]                 = topic.ContentType;
       routeData.Values          ["directory"]                   = requestContext.HttpContext.Request.Url.AbsolutePath;
-      routeData.Values          ["path"]                        = topic.GetUniqueKey();
+      routeData.Values          ["uniqueKey"]                   = topic.GetUniqueKey();
 
       /*------------------------------------------------------------------------------------------------------------------------
       | SET TARGET TYPES