Add Security information to Security Analytics documentation

[cwillum]

Description

Most plugins have a topic in their documentation that provides information about integration with the Security plugin. This adds an equivalent topic for Security Analytics

Issues Resolved

Created documentation that discusses basic permissions and backend roles for for Security Analytics
Fixes #3183

Checklist

• By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and subject to the Developers Certificate of Origin.
  For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[cwillum]

@opensearch-project/security Team, to begin organizing, defining, and rounding out permissions in the documentation, I took the opportunity to categorize cluster permissions and provide references to APIs while adding new permissions for Security Analytics. There are two cluster permissions, however, that I'm not clear on:

1. cluster:admin/reindex/rethrottle
2. cluster:admin/reroute

Do you know what these allow users to do and what API you would associate them with? Thanks.

[cwillum]

@sbcd90 @amsiglan Could one of you two have a look at the new security section I added for Security Analytics? It's borrowed from other plugins (e.g., alerting, anomaly detection) and includes information like basic roles for the plugin and how to use backend roles. It also cross references to the Permissions page in documentation. This now lists the permissions for Security Analytics.
I also began reorganizing all cluster permissions on this page. It probably wasn't a good idea to mix the two tasks. But I couldn't resist the change. You'll see a lot of that in the changes, too. Thanks.

[amsiglan]

@sbcd90 @amsiglan Could one of you two have a look at the new security section I added for Security Analytics? It's borrowed from other plugins (e.g., alerting, anomaly detection) and includes information like basic roles for the plugin and how to use backend roles. It also cross references to the Permissions page in documentation. This now lists the permissions for Security Analytics. I also began reorganizing all cluster permissions on this page. It probably wasn't a good idea to mix the two tasks. But I couldn't resist the change. You'll see a lot of that in the changes, too. Thanks.

Left a couple of comments, rest looks good to me

[vagimeli]

@cwillum Review completed. Minimal comments.

[cwillum]

@JeffH-AWS Thanks for the thorough review. The broken links you pointed out are now resolved.

[cwillum]

@here Just waiting for a final sign-off on this from doc team review comments.

[cwillum]

@JeffH-AWS please verify and OK changes so I can get this one out the door. Thanks.

Review feedback already implemented

[opensearch-trigger-bot]

The backport to 2.4 failed:

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

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

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

[opensearch-trigger-bot]

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

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

[opensearch-trigger-bot]

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

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

[cwillum]

Will revisit merge conflicts after 2.7 release.