[2.16] Fix minor issues for Direct Query Datasource

[RyanL1997]

This PR will be forwardported into both main and 2.x

Description

[2.16] Fix minor issues for Direct Query Datasource

Issues Resolved

• tabs order change
• support deletion in mds
• add acceleration creation flow into data connection table actions
• mute the integration access when mds is enabled or no observability plugin and add the integration creation flow
• add discover forwarding in data connection table
• mute the log explore forwarding when observability dashboards is not installed
• add log explore forwarding for s3 connections' action

Screenshot

Testing the changes

Changelog

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 42.85714% with 24 lines in your changes missing coverage. Please review.

Project coverage is 67.85%. Comparing base (587b319) to head (ca34f2b).
Report is 1 commits behind head on 2.16.

Files	Patch %	Lines
...ion/manage_direct_query_data_connections_table.tsx	26.66%	20 Missing and 2 partials ⚠️
.../data_source_management/public/components/utils.ts	77.77%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             2.16    #7419      +/-   ##
==========================================
- Coverage   67.87%   67.85%   -0.02%     
==========================================
  Files        3589     3589              
  Lines       72327    72354      +27     
  Branches    11838    11844       +6     
==========================================
+ Hits        49091    49095       +4     
- Misses      20245    20265      +20     
- Partials     2991     2994       +3     

Flag	Coverage Δ
Linux_1	33.49% <ø> (-0.01%)	⬇️
Linux_2	55.66% <ø> (ø)
Linux_3	44.44% <42.85%> (-0.02%)	⬇️
Linux_4	34.19% <11.11%> (-0.01%)	⬇️
Windows_1	33.51% <ø> (-0.01%)	⬇️
Windows_2	55.61% <ø> (ø)
Windows_3	44.46% <42.85%> (-0.02%)	⬇️
Windows_4	34.19% <11.11%> (-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.

[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.

[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.

[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.

[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.

[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.

[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.

[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.

[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.

[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.

[RyanL1997]

also the build test failure is unrelated to this change: https://github.com/opensearch-project/OpenSearch-Dashboards/actions/runs/10072759210/job/27845358410?pr=7419#step:17:2014

[opensearch-trigger-bot]

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

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

[opensearch-trigger-bot]

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

[RyanL1997]

I will manual create the forward-port