Moving Query Workbench to Dev Tools

[TackAdam]

Description

This change migrates query workbench to dev tools for the navigation changes planned for 2.16. The way the selectedMDSDataConnectionId was passed needed to be updated to allow dev tools to correctly find data sources.

Working with MDS:

Screen.Recording.2024-07-11.at.6.15.05.PM.mov

Working with Flint:
FlintTest.mov.zip

There is an existing issue I outlined in #348. But testing with Flint(using dashboards-observability prior to the opensearch-project/dashboards-observability@19d68b2 commit) seems to keep all functionality working correctly.

Issues Resolved

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.

[sumukhswamy]

nit. could you rename all the dataSourceId to dataSourceMDSId, will be easier to distinguish

[ps48]

1. Can we please add the legacy UR support for workbench: https://github.com/opensearch-project/dashboards-observability/blob/7566cff5e9a245cc619732741e05886617134e8e/public/plugin.tsx#L187-L190

   So If user types https://playground.opensearch.org/app/opensearch-query-workbench they’ll be redirected to https://playground.opensearch.org/app/dev_tools#/opensearch-query-workbench

2. Let's fix the linter errors here.
   Thanks!

[ps48]

@TackAdam Did we test this with and without new nav? cc: @sumukhswamy

[ps48]

Thanks! Sumukh for validating offline that workbench works with MDS with and without new nav.

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