Create a proof of concept for onboarding and detecting new releases

[peternied]

Create a simple project* that would produce a release artifact. Make a 1.0.0 release, a 1.1.0 release, and a 1.1.1 release. Following the notions of what has been described in the overall release process. Afterward determine sharp edges that can be improved.

*: language of your choice

Acceptance Criteria:

• Create the test release project
• Create the workflow
• Figure out docker management
• Create follow up issues before rolling out.
• Create final list of features that are needed to roll out the universal release process on [Meta] Create universal mechanism for releasing OpenSearch clients #1234

[peternied]

I've got a basic workflow, https://github.com/peternied/data-prepper/pull/new/uni-poc still need to make sure there is glue on the other side and confirm the jenkins connection.

I've created a fresh CI instance to make sure I'm not depending on our existing logic following https://github.com/opensearch-project/opensearch-ci dev deployment

[peternied]

I have created a proof of concept workflow tested within a jenkins instance:

• Implementation for sign, promote, maven, docker, ecr for Data Prepper, PR
• Implementation for centrally managed pipeline in OpenSeach-Build, PR
• Workflow output, console log

Break down of the work needed to productize this flow:

• Create the standard release pipeline + test helpers to mock out functionality
• Confirm the shared boiler plate code for the library import, parameters, workflow, and any additional pipeline configuration
• Create publishToMaven function
• Create publishToArtifactRepositry function
• Work backwards on what the distribution manifest should include that is missing, or create additional parameters in the job
• Create a DistManifest class
• Update Dist manifest in python to follow the new schema

[peternied]

Updated the recent associated PR to include the potential manifest changes, and reviewed with Data Prepper team.