Updates create accelerations flyout usage and side tree

[ps48]

Description

Updates create accelerations flyout usage and side tree

Issues Resolved

1. Updates create accelerations flyout
2. Uses accelerations details flyout
3. Updates side is sql to use cache

Check List

• New functionality includes testing.
  • All tests pass, including unit test, integration test and doctest
• New functionality has been documented.
  • New functionality has javadoc added
  • New functionality has user manual doc added
• Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 59.34%. Comparing base (997c666) to head (bcb9c7a).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #285      +/-   ##
==========================================
- Coverage   61.47%   59.34%   -2.13%     
==========================================
  Files          33       39       +6     
  Lines        1599     1835     +236     
  Branches      284      328      +44     
==========================================
+ Hits          983     1089     +106     
- Misses        518      633     +115     
- Partials       98      113      +15     

Flag	Coverage Δ
dashboards-query-workbench	59.34% <ø> (-2.13%)	⬇️

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.

[mengweieric]

nit. if selectedItems and refreshTree are required dependencies for loadTree, then it's better to explicitly pass them in since you are declared them in dependency array

[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/dashboards-query-workbench/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/dashboards-query-workbench/backport-2.x
# Create a new branch
git switch --create backport/backport-285-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 d168db7402d077681d895309ebe05a50e8880e72
# Push it to GitHub
git push --set-upstream origin backport/backport-285-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/dashboards-query-workbench/backport-2.x

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

[opensearch-trigger-bot]

The backport to 2.13 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/dashboards-query-workbench/backport-2.13 2.13
# Navigate to the new working tree
pushd ../.worktrees/dashboards-query-workbench/backport-2.13
# Create a new branch
git switch --create backport/backport-285-to-2.13
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 d168db7402d077681d895309ebe05a50e8880e72
# Push it to GitHub
git push --set-upstream origin backport/backport-285-to-2.13
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/dashboards-query-workbench/backport-2.13

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