[META] Move snapshot build jobs out of distribution build jobs

[bbarani]

Problem:

Currently the snapshot jobs are tightly coupled with monolithic distribution build job creating single point of failure and bottleneck for day to day development.
There are 2 kinds of snapshots:

1. Min tarball snapshot: This is core/engine/min only snapshot available as a tarball and accessible via https://artifacts.opensearch.org/snapshots/core/opensearch/....
   More details: https://github.com/opensearch-project/opensearch-build#min-snapshots
2. Maven snapshots: These are the snapshots published on nexus accessible via https://aws.oss.sonatype.org/content/repositories/snapshots/org/opensearch/ and includes all components including plugins.

1. is not an issue today and is independent of any components. However, 2) is a tightly coupled workflow.
   The maven snapshots are published based on input manifest where if one of the component fails to build, the entire snapshot publication to maven is abandoned. We will need to move the snapshot job outside of distribution build jobs in to its own job / have the respective repos publish snapshots via GitHub actions to de-centralize the publishing process.

Solution

The move tightly coupled workflows can be decoupled by moving snapshot publication to each component repository. The credentials to publish snapshot can be retrieved via AWS GHA integration that is already set in place

We tried this solution with security plugin and it works well. https://github.com/opensearch-project/security/actions/runs/4206453061

Child issues with all backend plugins:

• Publish maven snapshots using GitHub Actions OpenSearch#6365
• Publish snapshots to maven via GHA alerting#802
• Publish snapshots to maven via GHA anomaly-detection#813
• Publish snapshots to maven via GHA asynchronous-search#239
• Publish snapshots to maven via GHA index-management#689
• Publish snapshots to maven via GHA job-scheduler#319
• Publish snapshots to maven via GHA k-NN#771
• Publish snapshots to maven via GHA performance-analyzer#385
• Publish snapshots to maven via GHA sql#1358
• Publish snapshots to maven via GHA observability#1414
• Publish snapshots to maven via GHA notifications#620
• Publish snapshots to maven via GHA cross-cluster-replication#710
• Publish snapshots to maven via GHA common-utils#361
• Publish snapshots to maven via GHA reporting#648
• Publish snapshots to maven via GHA ml-commons#734
• Publish snapshots to maven via GHA geospatial#225
• Publish snapshots to maven via GHA security-analytics#334
• Publish snapshots to maven via GHA neural-search#114
• Publish snapshots to maven security#2438
• Publish maven snapshots using GitHub Actions opensearch-testcontainers#75

[gaiksaya]

Related #1182

[jordarlu]

The plan is to move the snapshot publication to each individual repo