[Workspace]Fix maximum call stack error in use case service

[wanglam]

Description

This PR is for fixing maximum call stack error in use case service, separate a function to compare features using sort instead of using Array.property.some.
The root cause of this bug should be error features compare result see below example:

// use case 1
{
    features:[{id:"1"},{id:"2"}]
}
// use case 2
{
    features:[{id:"1"},{id:"2"}]
}

The result should be true which means two use case should be equal. But the old compare logic will return false. We should change b.features.some to b.features.every, then the result would be correct. Using some and every to implement the compare logic would be a little bit complicated, it can't handle duplicate features. So we change to use sort to compare the use case.

Issues Resolved

#7820

Screenshot

No UI changes

Testing the changes

• Clone branch code and run yarn osd bootstrap --single-version ignore
• Add below configs in config/opensearch_dashboards.yml

workspace.enabled: true
uiSettings:
  overrides:
    'home:useNewHomePage': true

• Run yarn start --no-base-path
• Login and visit workspace detail page
• Open devtools and should no Maximum call stack error in the console

Changelog

• fix: [Workspace] maximum call stack error in use case service

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

All modified and coverable lines are covered by tests ✅

Project coverage is 63.83%. Comparing base (3364d0c) to head (5508ff0).
Report is 11 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #7817   +/-   ##
=======================================
  Coverage   63.82%   63.83%           
=======================================
  Files        3658     3658           
  Lines       81286    81288    +2     
  Branches    12975    12974    -1     
=======================================
+ Hits        51884    51888    +4     
+ Misses      26217    26216    -1     
+ Partials     3185     3184    -1     

Flag	Coverage Δ
Linux_1	30.16% <100.00%> (+<0.01%)	⬆️
Linux_2	55.87% <ø> (ø)
Linux_3	40.42% <ø> (+<0.01%)	⬆️
Linux_4	31.29% <ø> (ø)
Windows_1	30.18% <100.00%> (+<0.01%)	⬆️
Windows_2	55.82% <ø> (ø)
Windows_3	40.42% <ø> (ø)
Windows_4	31.29% <ø> (ø)

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]

Perhaps we can simplify the compare by sorting the serialized array and see if JSON.stringify(sortArray) equals?

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