[BUILDKITE] trigger publishing

[gogochan]

Change Summary

https://github.com/elastic/security-team/issues/6786

This PR wires up Buildkite Package publishing. It also disable publishing via Jenkins by setting DRY_RUN=TRUE.
Once merged, the artifact will be published using Buildkite only.

Sample execution:
https://buildkite.com/elastic/endpoint-package/builds/227

Remaining work

• Buildkite doesn't block PR at the moment.
• Remove Jenkins pipeline after validation.

Sample values

There's no sample as this is CI only thing.

Release Target

Q/A

For mapping changes:

• I ran make after making the schema changes, and committed all changes
• If these field(s) are "exception"-able, I made a companion PR to Kibana adding it (see Readme)
• If this is a metadata change, I also updated both transform destination schemas to match

For Transform changes:

• The new transform successfully starts in Kibana
• The corresponding transform destination schema was updated if necessary

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2024-01-09T17:13:17.041+0000

• Duration: 7 min 20 sec

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.