Add start-opensearch action

[derek-ho]

Description

This PR adds a start-opensearch action to this shared repo. There are many instances of plugins in their own CI spinning up their own opensearches to test against, and there is a lot of duplicate code out there.

Examples:
https://github.com/opensearch-project/security/blob/main/.github/actions/start-opensearch-with-one-plugin/action.yml
https://github.com/opensearch-project/security-dashboards-plugin/blob/main/.github/actions/run-cypress-tests/action.yml#L38
https://github.com/opensearch-project/dashboards-observability/blob/main/.github/workflows/ftr-e2e-dashboards-observability-test.yml#L49

I would like to get some maintainers views on the path forward to getting this in and used in repos across the project.

Issues Resolved

List any issues this PR will resolve, e.g. Closes [...].

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.

[peternied]

This repository serves as a focal point for practices that apply to all repositories in OpenSearch, this GitHub action seems to fill a useful role - but that role does not apply to the project website, data prepper, or many other non-plugin projects.

There has been discussion about how/where these kinds of tools go

• [FEATURE] Managing Reusable GitHub Actions #105

I suspect managing your own repo for an individual GitHub Action will be the fastest way to get started and then migrate if/when there is a better home.

Other areas to consider, there is a template for all plugins that might make sense from a centralization approach that best fits this use case.

• opensearch-plugin-template-java

---

I don't think there is a clear path forward for this pull request, but I'll keep it open for a week so others can comment and provide guidance - thanks @derek-ho

[dblock]

Another option is https://github.com/opensearch-project/opensearch-plugins. But I agree that a standalone action published to the GitHub Actions marketplace is probably best.

I propose we close this without merging?

[derek-ho]

Sure, closing. For reference I created the proposed action(s) under my own github