Inconsistent handling of browser history and routes

[pbochynski]

Description
Navigation in busola is not deterministic:

1. Path-based routing shows error messages before the correct view is displayed. You can reproduce it on any view that is registered by extension. Example: go to Service Management -> Service Instances. Now go to the address bar of the browser and hit enter (return). The page is reloaded but before the correct view is displayed a user can see the message:
   
2. When the user navigates between views the browser history gets 2 entries for each page (one with Busola and other with name of the view:

The history should contain only Secrets and Config Maps entries. If I want to go back to the previous view I need to press back button twice.

3. History navigation doesn't work at all with navigation nodes introduced by extensions. If you do the same exercise as before with switching between Service Instances and Service Bindings, the browser back button has no effect and the displayed content. The active navigation node and the URL in the address bar will change, but you also need to hit back button twice to go back to the previous url.

Expected result

1. I can open link to the custom view in busola without seeing incorrect path message.
2. I can navigate to the previous/next view with browser history buttons.