[Workspace] use registered nav groups in workspace form

[wanglam]

Description

In 2.15, we add the workspace use case selector in the workspace form. It used a fixed use cases list. In #7060 , we added a new concept nav group. The workspace form should use these registered nav groups as use cases and displayed in the workspace use case selector. This PR mainly includes below changes:

1. Add available use cases property in workspace selector
2. Subscribe registered use cases in the workspace plugin
3. Pass registered use cases to workspace selector
4. Remove not used workspaceConfigurableApps$

Issues Resolved

#7222

Screenshot

No UI changes

Testing the changes

The nav groups have not been displayed in the navigation, so we need to use unit tests to verify all changes.

• For getRegisteredUseCases$ inside use case service
  Can refer src/plugins/workspace/public/services/use_case_service.test.ts
• For app updater and registeredUseCase subscription
  Can refer src/plugins/workspace/public/plugin.test.ts
• For workspace creator / updater / overview functionality
  Can refer below files:
  src/plugins/workspace/public/components/workspace_creator/workspace_creator.test.tsx
  src/plugins/workspace/public/components/workspace_updater/workspace_updater.test.tsx
  src/plugins/workspace/public/components/workspace_overview/workspace_overview.test.tsx

Changelog

• feat: Use registered nav group as workspace use case

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

[github-actions]

❌ Empty Changelog Section

The Changelog section in your PR description is empty. Please add a valid changelog entry or entries. If you did add a changelog entry, check to make sure that it was not accidentally included inside the comment block in the Changelog section.

[codecov]

Codecov Report

Attention: Patch coverage is 94.52055% with 4 lines in your changes missing coverage. Please review.

Project coverage is 67.53%. Comparing base (38ae65b) to head (6aafb87).
Report is 313 commits behind head on main.

Files with missing lines	Patch %	Lines
src/plugins/workspace/public/plugin.ts	90.47%	0 Missing and 2 partials ⚠️
...rkspace/public/components/workspace_list/index.tsx	83.33%	0 Missing and 1 partial ⚠️
...gins/workspace/public/services/use_case_service.ts	92.85%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #7221      +/-   ##
==========================================
+ Coverage   67.52%   67.53%   +0.01%     
==========================================
  Files        3501     3502       +1     
  Lines       69340    69372      +32     
  Branches    11303    11311       +8     
==========================================
+ Hits        46824    46853      +29     
+ Misses      19764    19762       -2     
- Partials     2752     2757       +5     

Flag	Coverage Δ
Linux_1	33.15% <94.52%> (+0.04%)	⬆️
Linux_2	55.46% <ø> (ø)
Linux_3	43.05% <ø> (-0.02%)	⬇️
Linux_4	34.71% <ø> (ø)
Windows_1	33.20% <94.52%> (+0.04%)	⬆️
Windows_2	55.41% <ø> (ø)
Windows_3	43.06% <ø> (ø)
Windows_4	34.71% <ø> (-0.01%)	⬇️

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.

[SuZhou-Joe]

Do we need to check if the use case from constant equal to the one from navGroup? I thought match on id should be good enough.

[wanglam]

For now, the isEqualWorkspaceUseCase only been used in UseCaseService. It's just for avoid duplicate changes fired. The appUpdater$ in filterNavLinks will generate new nav links. Then the getNavGroupsMap$ will emit new nav groups map. It will generate an infinite loop. So we add distinctUntilChanged after getNavGroupsMap$ to avoid these.

[SuZhou-Joe]

I c, thanks.