Opensearch security plugin windows install certs demo config and add batch install script

[peterzhuamazon]

Description

Add windows batch file and resolve security demo config temporarily.
Follow up: opensearch-project/security#2148

Issues Resolved

opensearch-project/security#2122

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-commenter]

Codecov Report

Merging #2704 (86e7304) into main (6b71a5f) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #2704   +/-   ##
=======================================
  Coverage   94.10%   94.10%           
=======================================
  Files         156      156           
  Lines        4208     4208           
=======================================
  Hits         3960     3960           
  Misses        248      248           

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

[peternied]

Quoting DB from #2061

Shouldn't you be committing this [scripts/components/security/install.sh] into the security plugin repo instead in the right branch?

Work around looks good to me - please work with @scrawfor99 if you'd like help staging things between here and the security repository

[peterzhuamazon]

Quoting DB from #2061

Shouldn't you be committing this [scripts/components/security/install.sh] into the security plugin repo instead in the right branch?

Hi,
Glad you bring up this question. As this PR is a completely different situation compares to the PR you raised in #2061.

I would suggest you to check these categories within the build repo code base a bit more and it should help you understand the reasoning better. Here are some few points that might interest you.

1. Check script finder class on how the install.sh being allocated.
(Yes, install.sh will not be allocated from the component repo directly)

2. Check dist and bundle code within assemble workflow to understand why it cannot be saved in plugin repositories. Understand the differences between build.sh and install.sh and how are they being processed.
(Build requires all components to be cloned thus scripts can exist in separate repos, but install will allocate only the artifacts on the build machines without the need to allocate other repos, or it will be a heavy operation.)

Additionally if you have time available I would suggest you contribute the functionalities to call install.sh from separate repositories if you would like this feature to be added. Bare in mind, this is a heavy operation and as of current state it is not required to be used for the assemble workflow.

Thanks.

[peterzhuamazon]

Work around looks good to me - please work with @scrawfor99 if you'd like help staging things between here and the security repository

Sure will work with @scrawfor99 when needed.
Thanks.

[peterzhuamazon]

Will force merge for now as the groovy test failure is not related to my code in this PR.
More information here: opensearch-project/opensearch-build-libraries#7 (comment)

Thanks.