Add Builkite-related actions to manipulate annotations and metadata

[AliSoftware]

What does it do?

1️⃣ Adds a buildkite_annotate action

Allows you to add a new annotation (providing a message, and an optional context and style), or delete an existing one, to/from the current CI build

if warnings.count > 0
  # Add a new annotation to surface e.g. some linter warnings using a nice markdown-formatted message
  markdown = "Linter found #{warnings.count} warnings: \n" + warnings.map { |msg, line| " - [#{msg}](\#L#{line}) }.join("\n")
  buildkite_annotate(context: 'lint-warnings', style: 'warning', message: markdown)
else
  # Remove an annotation with that given context if it exists (no-op if not)
  buildkite_annotate(context: 'lint-warnings', message: nil)
end

2️⃣ Adds a buildkite_metadata action

Allows you to set and get Buildkite metadata from the current CI build

buildkite_metadata(set: { key1: 'value1', key2: 'value2' })
buildkite_metadata(set: { 'version:name': version_name, 'version:code': version_code })
build_flavor = buildkite_metadata(get: 'flavor')

Checklist before requesting a review

• Run bundle exec rubocop to test for code style violations and recommendations
• Add Unit Tests (aka specs/*_spec.rb) if applicable
• Run bundle exec rspec to run the whole test suite and ensure all your tests pass
• Make sure you added an entry in the CHANGELOG.md file to describe your changes under the approprioate existing ### subsection of the existing ## Trunk section.

[spencertransier]

These actions and tests look great! The test cases were really helpful for getting an idea of how the actions work. TIL what the term "ctx" refers to, I hadn't run into that before 🙂