Adding index permissions for remote index in AD

[amitgalitz]

Description

Adding a few more index permissions for AD full access role. This is due to the fact we now make some additional calls during detector creation to get all necessary information from the remote clusters.

Issues Resolved

opensearch-project/anomaly-detection-dashboards-plugin#854

Is this a backport? If so, please add backport PR # and/or commits #, and remove backport-failed label from the original PR.

Do these changes introduce new permission(s) to be displayed in the static dropdown on the front-end? If so, please open a draft PR in the security dashboards plugin and link the draft PR here

Testing

[Please provide details of testing done: unit testing, integration testing and manual testing]

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 65.53%. Comparing base (31cfd54) to head (bd01a47).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4719      +/-   ##
==========================================
+ Coverage   65.51%   65.53%   +0.02%     
==========================================
  Files         319      319              
  Lines       22448    22448              
  Branches     3602     3602              
==========================================
+ Hits        14707    14712       +5     
+ Misses       5933     5927       -6     
- Partials     1808     1809       +1     

see 3 files with indirect coverage changes

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

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

[opensearch-trigger-bot]

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

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