[Meta] Enable smoke tests for OpenSearch distribution + plugins

[zelinh]

Based on feature request from #4551, we create this meta issue to keep track of all action items.

We proposed smoke test workflow provides a foundational framework to run quick checks on the OpenSearch bundle. These tests run separately from the more complex integration tests but follow a similar deployment process.

Introduce a smoke test framework to the CI/CD process. The workflow will pass parameters like the distribution path, architecture, and components.

Tasks:

• Add new smoke test section into test manifest schema #5126
  A new "smoke-test" section will be added to the manifest file to specify which components are onboarded for smoke testing.

• Onboard component test spec YAML and spec framework
  Each plugin will have a YAML file defining the smoke tests and associated API requests based on the OpenSearch API specification. The test specs will account for version differences in APIs.

• Create smoke test python workflow for cluster deployment and testing #5164
  The new introduced smoke test runner automates OpenSearch cluster deployment, loads test manifests, sends API requests, and validates responses against the OpenSearch API specification with third-party OpenAPI-core python client. It ensures all key components function immediately after a build.

• Integrate the smoke test workflow with CI/CD pipeline #5224
  The new Jenkins pipeline would be created to integrate smoke tests with existing build workflow for automation to catch major issue in earlier stage.

[zelinh]

We had an analysis on Consideration for Onboarding Smoke Tests to OpenSearch Dashboards.

[zelinh]

To onboard more OpenSearch plugins, we created a sub issue to keep track of the status.
Onboard Core and plugins for the Smoke test