[MD] new UX changes for password fields and update password modal in data source management

[mpabba3003]

Signed-off-by: mpabba3003 amazonmanideep@gmail.com

Description

new UX changes for password fields and update password modal in data source management

Issues Resolved

[List any issues this PR will resolve]
opensearch-project/ux#34

SCREENSHOTS

Data.Sources.-.OpenSearch.Dashboards.1.mp4

Check List

• All tests pass
  • yarn test:jest
  • yarn test:jest_integration
  • yarn test:ftr
• New functionality includes testing.
• New functionality has been documented.
• Update CHANGELOG.md
• Commits are signed per the DCO using --signoff

[codecov-commenter]

Codecov Report

Merging #2532 (5b68803) into main (ac07159) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main    #2532   +/-   ##
=======================================
  Coverage   66.74%   66.74%           
=======================================
  Files        3201     3201           
  Lines       60948    60951    +3     
  Branches     9267     9267           
=======================================
+ Hits        40679    40682    +3     
  Misses      18052    18052           
  Partials     2217     2217           

Impacted Files	Coverage Δ
...ent/public/components/text_content/text_content.ts	100.00% <100.00%> (ø)
...ared/static/forms/hook_form_lib/hooks/use_field.ts	65.70% <0.00%> (-0.97%)	⬇️
...ic/application/models/sense_editor/sense_editor.ts	64.00% <0.00%> (-0.89%)	⬇️
packages/osd-optimizer/src/node/cache.ts	52.77% <0.00%> (+2.77%)	⬆️
...s/osd-optimizer/src/node/node_auto_tranpilation.ts	87.75% <0.00%> (+4.08%)	⬆️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[ashwin-pc]

Ive called this out in some of the other MD PR's, but lets move the translate functions into the react components. That way we have realtime translations instead of static translations that only run during compile time.

[mpabba3003]

Understood, I will resolve it today in a different PR as many PRs will have conflicts if I do it now.

[mpabba3003]

#2543

[ashwin-pc]

Thanks @mpabba3003!

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

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