RoutingMiddleware causes endless redirection loops in some circumstances

[mrpmorris]

RoutingMiddleware dispatches a GoAction whenever NavigationManager.LocationChanged' is triggered and the new URL doesn't match the URL in the state, An Effect will then trigger to call NavigationManager.Navigate` if the state URL and current URL are different.

This allows us to ensure navigation occurs when dispatching GoAction, and that GoAction is dispatched when non-Fluxor code calls NavigationManager.Navigate.

When using Microsoft MSAL authentication the quick changing of URLs can cause in endless redirect loop.