[PLAN] Top contextual bar

Updated with a list of the remaining issues.

I'd also like to see what that top bar might look like in the context of viewing the published version (if one exists) or viewing the current draft. I'm not a big fan of hiding things under "more options"; can that be an individual user's preference setting? Some users probably prefer less clutter, others like me prefer my options to be in sight.

Adding reference to 📌 Create feature flag module to control navigation top bar visibility Fixed

more layout use please! (:

• Workspaces: add a 'tab' (only) and attaches js/css via library api (which opens the top fixed off-canvus drawer that is the Workspaces UI)
• Acquia Connector: add a tab (only) opens to external hosting tools dashboard.
• Devel: adds 'tab' and 'tray' of child menu item [see: \Drupal\devel\ToolbarHandler]
• Env Indicatior: general use cases, add a'tab'
• demo_umami: adds 'tab' item to say

It could use to provide help topics for the module

We're missing a breadcrumb more that a return link which then fills the space we need (sm->mid breakpoint ranges)

noting:
- right most icon is meant to be Node Forms vertical tabs
- actions include old style tab items (ie: revision, also normal for developers 'devel' would follow)

Replacing the screenshot posted to avoid confusion and discussions about unrelated elements on the page. Please take into account that this is still on the definition phase where we are actively defining (and testing) which features to provide.
Yes, the plan is to provide an plugable system for contribs and custom modules. But we still need to define where goes what and why, and after that provide the necessary documentation to help everybody make the best call. But as today we're not there yet :)

I think it is good place for
1. SDC.
Before SDC was stable we had some efforts in that direction https://git.drupalcode.org/project/navigation/-/merge_requests/72/diffs

We need to convert existing components and add new components as sdc.

2. Storybook. I still believe it is better to check all theories until they adapted on Drupal.

Some previous SB versions.
https://storied-pixie-3d54e7.netlify.app/iframe.html?args=&id=page-examp...
https://sparkling-gaufre-c402f2.netlify.app/iframe.html?args=&id=page--b...
https://thunderous-treacle-600c5c.netlify.app/iframe.html?args=&id=page-...

We started using layout builder in mega menu's awhile ago with great success, and seeing layout builder implemented in the new navigation builder successfully is awesome. I'd love to see it used here. We could have blocks for 'Entity Operations', 'Form Actions', etc. With the left toolbar acting more global, and the top bar holding more contextual info, we could take advantage of the existing Context system for some of the block visibility handling. This approach makes it far easier for other modules to extend and override the top bar without having to override templates everywhere.

I'd be happy to build that in similar fashion to the left hand toolbar if it would be helpful.