[chrome/nav] implement forcedNavigation logic in new nav

[spalger]

Summary

When the Kibana server is red we render the status page in place of the current page, kind of like an error page. This prevents us from having to worry about redirects, but also means that links which normally trigger navigation with hash changes are broken because the status page app is rendered instead of the current app. To fix this we enable "forced navigation" mode on the status page so that any nav bar link that is clicked, which resolves to the same protocol+host+path will trigger a page refresh.

This used to be implemented as a click handler on each nav item, but EUI doesn't support click handlers on links in the Nav, so this uses a single event listener at the container around the nav links which handles the click events which bubble up. This means the feature now also works for the recent links and the home link.

To test this you should start Kibana in oss mode as security prevents the display of the status page, since license info can't be retrieved.

1. node scripts/kibana --dev --oss without elasticsearch
2. open http://localhost:5601
3. on the status page, try clicking the app links, the page should refresh and attempt to load the clicked url
4. start es yarn es snapshot --license oss
5. wait for Kibana to go green
6. click an app link and the app should load correctly

Original implementation: https://github.com/spalger/kibana/blob/597062fcbd346c2e11f1266f54c041d4469f8dee/src/ui/public/chrome/directives/global_nav/app_switcher/app_switcher.js#L35-L61

[elasticmachine]

Pinging @elastic/kibana-platform

[elasticmachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request

[joshdover]

Not sure if it's important to this PR, but the steps above do not quite work for me. I get the message Kibana server is not ready yet if ES is not started. I can get to the status page if I start ES, let Kibana connect, and then shut down ES.

[joshdover]

Is this change necessary? Before your PR if you click on a NavLink that would trigger a hash change in Angular router, it appears to just stay on the status page. With this change, it refreshes the status page when you click on a navlink. Do we consider this current behavior broken? Is that refreshing worth the complexity of this change?

[spalger]

Is this change necessary? ... Do we consider this current behavior broken?

It's necessary in that it has been a "feature" since 4.2, and I think having app links that are clickable but don't work without refreshing the page considers them broken, personally.

[elasticmachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request

[joshdover]

LGTM, just want a some comments to help me remember what in the world this is later 😄

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request