add DRA version bump pipeline

[ninalee12]

Release notes

What does this PR do?

Hi Team,

This PR is the first phase of the version-bump automation rollout as mentioned in #mission-control. It introduces a generalized Buildkite pipeline for service teams in the DRA process. The baseline pipeline includes a block step that waits for each team to unblock before polling for DRA artifacts using a buildkite plugin json-watcher-buildkite-plugin for the polling.

Why is it important/What is the impact to the user?

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files (and/or docker env variables)
• I have added tests that prove my fix is effective or that my feature works

Author's Checklist

• [ ]

How to test this PR locally

Related issues

• https://github.com/elastic/observability-robots/issues/3404
• If you haven't already, please provide the Slack channel name for notifications via a comment here or on the issue listed above

Use cases

Screenshots

Logs

[github-actions]

🤖 GitHub comments

Just comment with:

• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)
• run exhaustive tests : Run the exhaustive tests Buildkite pipeline.

[mergify]

This pull request does not have a backport label. Could you fix it @ninalee12? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit.
• If no backport is necessary, please add the backport-skip label

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 69586c2

Failed CI Steps

• :java: Java unit tests

History

• 💚 Build #4348 succeeded 6afb2d2
• 💛 Build #4337 was flaky d7fee86