[FEATURE] Generalize Build/Install Plugin From Zip Workflow

[derek-ho]

Is your feature request related to a problem?
The original impetus for creating a build and install plugin from zip was here. The main problem being that simply running yarn test does not perform a comprehensive check. Instead, issues such as relative path imports, dev dependencies not being present, and public code not being available in the server module can only be caught when running from a binary, and not from a local setup.

Although we have existing infrastructure to catch these (such as autocuts), it makes sense to add this as a GHA such that any PR that goes into the main branch is ensured against these kinds of errors.

What solution would you like?
I would like to propose generalizing the existing flow within the security dashboards plugin, so that other dashboards plugins can re-use the workflow to ensure that the code builds and passes a basic health check against OSD.

Do you have any additional context?
Other cases where this common workflow might be helpful (outside of the cases mentioned in the impetus issue):

• [RELEASE] Release version 2.6.0 opensearch-build#3081 (comment)
• [RELEASE] Release version 2.12.0 opensearch-build#4115 (comment)

[DarshitChanpura]

[Triage] Thanks for filing this issue. @derek-ho is following up on this with a PoC.

[peternied]

If we are going to generalize these actions, I'd recommend moving them out into their own repositories so they are decoupled from the Security plugins version. Let me know if you'd like a hand with this.

[derek-ho]

Published here: https://github.com/derek-ho/start-opensearch. Two PRs related to this:
opensearch-project/security#4063
#1783
Once I move the dashboards installation into a separate action we can close this issue, since other repos can then just use the start-opensearch and start-opensearch-dashboards actions to setup CI envs.