[MDS] Adds datasource filter for version decoupling

[DarshitChanpura]

Description

This change adds a datasource filter function to allow for version decoupling for MDS feature.

Category

Enhancement

Why these changes are required?

To allow for version decoupling in MDS.

What is the old behavior before changes and new behavior after changes?

Before: Datasources with all versions were shown.
After: Datasource with only compatible versions are shown.

Issues Resolved

• Resolves [FEATURE] Support Version Decoupling in Security Dashboards Plugin #1971

Testing

Unit tests

Check List

• New functionality includes testing
  - [ ] New functionality has been documented
• 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 69.46%. Comparing base (a44e265) to head (df825d7).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2051      +/-   ##
==========================================
+ Coverage   69.34%   69.46%   +0.11%     
==========================================
  Files          96       96              
  Lines        2587     2597      +10     
  Branches      375      386      +11     
==========================================
+ Hits         1794     1804      +10     
  Misses        699      699              
  Partials       94       94              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[derek-ho]

See comment: https://github.com/opensearch-project/security-dashboards-plugin/pull/2051/files#r1688545956

[DarshitChanpura]

See comment: https://github.com/opensearch-project/security-dashboards-plugin/pull/2051/files#r1688545956

#2051 (comment)

addressed to unblock this PR.

[derek-ho]

Does the yarn.lock need to be updated?

[derek-ho]

Lets take a look at the cypress failures for MDS to make sure there are no regressions prior to merging

Changes have been addressed. MDS cypress tests are no longer failing.

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

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.x 2.x
# Navigate to the new working tree
cd .worktrees/backport-2.x
# Create a new branch
git switch --create backport/backport-2051-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 e9609acc76e7db541eb3701bd53369555a98517c
# Push it to GitHub
git push --set-upstream origin backport/backport-2051-to-2.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.x

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

[opensearch-trigger-bot]

The backport to 2.16 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.16 2.16
# Navigate to the new working tree
cd .worktrees/backport-2.16
# Create a new branch
git switch --create backport/backport-2051-to-2.16
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 e9609acc76e7db541eb3701bd53369555a98517c
# Push it to GitHub
git push --set-upstream origin backport/backport-2051-to-2.16
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.16

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