Bug fixes to support mds in getSeverFeatures API

[riysaxen-amzn]

Description

This PR fixes the bug in MDS support for Notifications. Changes introduced:

• The issue is getSeverFeatures API should take the dataSourceId to return the response as per the provided dataSource
• getServerFeatures API should be called whenever a component updates to update the states as per the dataSource
• Also, removes some unused import from public/components/MDSEnabledComponent/MDSEnabledComponent.tsx

Issues Resolved

getSeverFeatures API call to support MDS is fixed

Check List

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

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

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