[navigation] display workspace picker content when outside workspace and nav group

[SuZhou-Joe]

Description

Left navigation will always be expandable in 2.17, and in order to prevent user creating objects in global when workspace is enabled, we will show workspace picker when outside workspace and nav group.

• Display workspace picker content when outside workspace and nav group
• Only register global index pattern page when workspace is disabled.
• Split src/core/public/chrome/ui/header/collapsible_nav_group_enabled.tsx to two files.
• Append manage category when:
  • Workspace enabled and out of workspace or nav group.
  • Workspace disabled and in all nav group.
• Always show expand / collapsed icon.
• Hide home from new left nav.

Issues Resolved

Screenshot

Workspace enabled and outside any workspace or nav group

Workspace disabled

Testing the changes

Changelog

• feat: display workspace picker content when outside workspace

Check List

• All tests pass
  • yarn test:jest
  • yarn test:jest_integration
• New functionality includes testing.
• New functionality has been documented.
• Update CHANGELOG.md
• Commits are signed per the DCO using --signoff

[codecov]

Codecov Report

Attention: Patch coverage is 89.04110% with 16 lines in your changes missing coverage. Please review.

Project coverage is 64.18%. Comparing base (6931a41) to head (3096bea).
Report is 9 commits behind head on main.

Files	Patch %	Lines
...chrome/ui/header/collapsible_nav_group_enabled.tsx	84.90%	0 Missing and 8 partials ⚠️
...public/chrome/ui/header/collapsible_nav_groups.tsx	87.09%	1 Missing and 3 partials ⚠️
src/core/public/chrome/ui/header/header.tsx	0.00%	0 Missing and 2 partials ⚠️
.../plugins/index_pattern_management/public/plugin.ts	66.66%	0 Missing and 1 partial ⚠️
...kspace_picker_content/workspace_picker_content.tsx	96.66%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #7716      +/-   ##
==========================================
+ Coverage   63.86%   64.18%   +0.31%     
==========================================
  Files        3665     3661       -4     
  Lines       81441    80842     -599     
  Branches    12994    12882     -112     
==========================================
- Hits        52010    51885     -125     
+ Misses      26243    25770     -473     
+ Partials     3188     3187       -1     

Flag	Coverage Δ
Linux_1	30.30% <27.27%> (+0.11%)	⬆️
Linux_2	55.92% <86.91%> (+0.04%)	⬆️
Linux_3	40.66% <3.63%> (+0.26%)	⬆️
Linux_4	31.45% <5.45%> (+0.07%)	⬆️
Windows_1	30.32% <27.27%> (+0.09%)	⬆️
Windows_2	55.87% <86.91%> (+0.04%)	⬆️
Windows_3	40.65% <3.63%> (+0.25%)	⬆️
Windows_4	31.45% <5.45%> (+0.07%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[opensearch-trigger-bot]

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/OpenSearch-Dashboards/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/OpenSearch-Dashboards/backport-2.x
# Create a new branch
git switch --create backport/backport-7716-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 56fc8f4057c1d6b3e58f4b77394f9bf8c4a9447c
# Push it to GitHub
git push --set-upstream origin backport/backport-7716-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/OpenSearch-Dashboards/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-7716-to-2.x.

[opensearch-trigger-bot]

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/OpenSearch-Dashboards/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/OpenSearch-Dashboards/backport-2.x
# Create a new branch
git switch --create backport/backport-7716-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 56fc8f4057c1d6b3e58f4b77394f9bf8c4a9447c
# Push it to GitHub
git push --set-upstream origin backport/backport-7716-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/OpenSearch-Dashboards/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-7716-to-2.x.

[AMoo-Miki]

Manually backported with #7882