Updates references to security demo configuration

[DarshitChanpura]

Description

Describe what this change achieves.

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.

[DarshitChanpura]

@Xtansia @VachaShah I would need your help to ensure that this instance where the demo script is being called:

opensearch-net/abstractions/src/OpenSearch.OpenSearch.Ephemeral/Tasks/InstallationTasks/InitialConfiguration.cs

Line 52 in f1df48d

cluster.Writer?.WriteDiagnostic($"{{{nameof(InitialConfiguration)}}} going to run [{securityInstallDemoConfigSubPath}]");

After doing some research I was able to move up chain of calls and it starts here: https://github.com/opensearch-project/opensearch-net/blob/main/abstractions/src/OpenSearch.OpenSearch.Managed/ClusterBase.cs#L127

[DarshitChanpura]

If I'm interpreting the github actions correctly, the integration tests do not run with security correct?

[derek-ho]

opensearch-project/security#3624

[derek-ho]

We can merge this once it's out of draft

[DarshitChanpura]

@Xtansia would you help bring this across finish line?

[dblock]

@DarshitChanpura what remains to be done? Mark it as ready if you're ready.

[Xtansia]

@DarshitChanpura @dblock I have been working on this, but I'm currently still on leave until the 8th atm. This shouldn't block the 2.12 release as we don't automatically pick up the new version here and the client is not in sync with core versioning/releasing anyways

[Xtansia]

@DarshitChanpura @dblock This is now ready for review and passing tests against unreleased 2.x & main.

[DarshitChanpura]

Thank you @Xtansia for taking this over.

[DarshitChanpura]

LGTM. Thank you once again @Xtansia.

[Xtansia]

@dblock Could we please get your review on this?

[dblock]

@dblock Could we please get your review on this?

This isn't needed until 2.12 and should not be passing until then, shouldn't it?

[Xtansia]

@dblock We do actually already hit the code paths in this PR because we test against 2.x and main with the security plugin installed. It's just that the tests against unreleased OpenSearch had been disabled due to breakage, which is now fixed and re-enabled in this PR. So all that's left for follow up is adding 2.12 to the released versions matrix when it's released. And all the changes are behind version checks

[opensearch-trigger-bot]

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

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