Add pinning capability to new navigation

[ryankeairns]

Relates to #64018

Describe the feature:
As a user, I would like to be able to pin the applications that I use most frequently for quick navigation.

Describe a specific use case for the feature:
Stop me if you've heard this one before 😆 ... Kibana has a lot of applications; individual users tend to rely upon a small subset; we should make it easier for them to navigate. By adding pinning capability, customers can fix their most used applications to the top of the new left navigation design and avoid visually scanning through the groups/lists in order to find what they need.

**** Technical considerations

The EuiCollapsibleNav component already provides the UI for this interaction and its docs example demonstrates the use of localStorage. The plan for Kibana is to also use localStorage with future consideration for another storage mechanism as alternatives come into existence.

**** Design mockup

cc:/ @alexfrancoeur

[elasticmachine]

Pinging @elastic/kibana-core-ui (Team:Core UI)

[ThomThomson]

I wonder how this will relate to some of the requests from #99740. Perhaps some of that functionality could be incorporated here:

Off the top of my head:

• What if we allowed individual dashboards to be pinned in this manner?
• Is there a way we can store this in the configuration for the space rather than in the localStorage, so that each user gets the same pinned items?

[ryankeairns]

A few additional places also come to mind:

• surfacing favorites/pinned items in the nav search
• adding favorites to the Dashboard homepage and allowing to filter on them/sort them to the top
• the home page is destined to contain dynamic contain, another place we could have favorites for this Space

The left nav component (this issue) was designed to handle pinning and, to me, the home page favoriting option also seems relatively straightforward / easy to fit into an existing view. The nav search and homepage will take more time.

[GrahamHannington]

Ideally, I'd like this issue (and issue #99740, which I submitted) to be considered in the context of an integrated method for app packaging and deployment.

By "app", I mean, more specifically, the following collection of related artifacts (this list might not be comprehensive):

• Kibana saved objects, including dashboards, and their visualizations, saved searches, and index patterns
• A multilevel list of links to the dashboards (as per issue Custom nested (cascading, flyout) menus of links in the Kibana sidebar #99740)
• Elasticsearch index templates
• Logstash configurations
• A Kibana Space definition

I mention a Kibana Space definition because, to me—perhaps idiosyncratically—a Kibana Space offers a method for encapsulating the Kibana saved objects for what I think of—again, perhaps idiosyncratically—as an "app". And a Space allows you to specify a "home" dashboard, and an icon, for that "app".

With apologies, I feel awkward and inadequate adding this comment here. I feel that I should be adding this comment to an issue about app packaging, and referring from there to this issue. However, I've not found what I consider to be that appropriate other "app packaging" issue. (I strongly suspect it exists, but I just haven't looked hard enough.)

[ryankeairns]

Thanks Graham!

cc:/ @alexfrancoeur you may be interested in this feedback, as well.