Create Breadcrumb Navigation Container

[pickypg]

The impetus came from #7380. Currently, it's up to plugins to create the breadcrumb navigation and do it properly themselves.

This can only lead to different implementations and therefore different styles, which will detract from the overall experience when jumping from plugin-to-plugin, as well as make plugin development a small-bit harder when trying to match the native experience (and even official plugins face this burden).

We should encapsulate this behavior in Kibana itself so that pages can establish their breadcrumbs and tabs or title, as well as which tab is currently selected. In doing so, this can help us to establish certain rules that keep the behavior both looking and feeling consistent.

Some rules that need to be maintained:

• When displaying tabs, they all need to have a link.
• Tabs need to be limited to a reasonable (aka arbitrary, but small) number.
• Which tab is active (required).
• Titles (aka singular tabs) should not have links.
• You cannot have both a title and tabs.
• Breadcrumbs should not include the tabs (thus hopefully implying that they're actually breadcrumbs).

From there, we can take those inputs and build the entire top bar, possibly including a capacity to add both custom and non-custom, but optional content to it (e.g., the pause/play and time controls currently live there).

[timroes]

cc @elastic/kibana-platform @elastic/kibana-design I think that issue might be outdated with regards to the new K7 design. Could someone approve on that and close it?

[snide]

Correct. This is mostly laid out through the introduction of the header in the K7 designs.

https://elastic.github.io/eui/#/layout/header