Fixed assignment of CurrentWebPath

In a previous update, we replaced `NavigationViewModel<T>`'s `CurrentKey` property with `CurrentWebPath`, in anticipation of it operating off of the URL, instead of the `UniqueKey` (8fd4d80). Unfortunately, in doing so, I missed that the _assignment_ of the `CurrentWebPath` was still pulling data from `CurrentTopic.GetUniqueKey()`—and, thus, calls to e.g. `NavigationTopicViewModel.IsSelected()` were failing, since it is now comparing against `webPath`.

Author: JeremyCaney

OnTopic.AspNetCore.Mvc/Components/MenuViewComponentBase{T}.cs

@@ -131,7 +131,7 @@ public async Task<IViewComponentResult> InvokeAsync() {
       \-----------------------------------------------------------------------------------------------------------------------*/
       var navigationViewModel = new NavigationViewModel<T>() {
         NavigationRoot = await MapNavigationTopicViewModels(navigationRootTopic).ConfigureAwait(true),
-        CurrentWebPath = CurrentTopic?.GetUniqueKey()?? HttpContext.Request.Path
+        CurrentWebPath = CurrentTopic?.GetWebPath()?? HttpContext.Request.Path
       };
 
       /*------------------------------------------------------------------------------------------------------------------------

OnTopic.AspNetCore.Mvc/Components/PageLevelNavigationViewComponentBase{T}.cs

@@ -128,7 +128,7 @@ public async Task<IViewComponentResult> InvokeAsync() {
       \-----------------------------------------------------------------------------------------------------------------------*/
       var navigationViewModel = new NavigationViewModel<T>() {
         NavigationRoot = await MapNavigationTopicViewModels(navigationRootTopic).ConfigureAwait(true),
-        CurrentWebPath = CurrentTopic?.GetUniqueKey()?? HttpContext.Request.Path
+        CurrentWebPath = CurrentTopic?.GetWebPath()?? HttpContext.Request.Path
       };
 
       /*------------------------------------------------------------------------------------------------------------------------