[navigation-next]fix: breadcrumb issue found in data source management and other similar cases.

[SuZhou-Joe]

Description

This PR fixes the issue that breadcrumbs do not function correctly in the new application when navigation feature flag is turned on.

When new navigation is turned on, we add 4 new applications: assets / index pattern management / data sources management / application settings to left navigation.

They used to work as sub applications within Dashboard management because the parent application adds intercept on the setBreadCrumbs to make the breadcrumb comply with the BrowserRouter and inherit the parent history from OSD core.

While after migrated to standard application in left navigation, these 4 applications are using core.chrome.setBreadCrumbs to update the breadCrumb, which do not have support BrowserRouter.

The change will only take effect when feature flag enabled, it won't have any impact on the existing application.

• Resolve the breadcrumb issue
• Make left navigation expandable in home page when workspace is enabled
• Make workspace overview visible in all use case

Issues Resolved

Screenshot

Before the fix

20240723175723455.mp4

After the fix

20240723175850857.mp4

Testing the changes

Changelog

• fix: make breadcrumb of 4 new added applications comply with BrowserRouter.

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

[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-7401-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 3f78c94e640209027d9e7cc5cd349403f70dea18
# Push it to GitHub
git push --set-upstream origin backport/backport-7401-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-7401-to-2.x.

[opensearch-trigger-bot]

The backport to 2.16 failed:

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

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.16 2.16
# Navigate to the new working tree
pushd ../.worktrees/OpenSearch-Dashboards/backport-2.16
# Create a new branch
git switch --create backport/backport-7401-to-2.16
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 3f78c94e640209027d9e7cc5cd349403f70dea18
# Push it to GitHub
git push --set-upstream origin backport/backport-7401-to-2.16
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/OpenSearch-Dashboards/backport-2.16

Then, create a pull request where the base branch is 2.16 and the compare/head branch is backport/backport-7401-to-2.16.