[backport-cloud_asset_inventory-1.4] Sync CI configuration with main branch

[mrodm]

TL;DR

Syncs .buildkite and .github CI configuration from main to the
backport-cloud_asset_inventory-1.4 backport branch.

This brings automated backport workflows, new CI scripts, Go tooling, and
GitHub Actions that only work when they are present on the target branch itself.

What does this PR do?

Syncs the following CI configuration from main onto the backport-cloud_asset_inventory-1.4 branch:

• Buildkite — updated hooks (post-checkout, pre-command, pre-exit), pipeline definitions (backport dispatch, publish, schedule-daily, schedule-weekly, serverless, main), and pull-requests.json; adds new scripts for backport orchestration, changelog checks, owner validation, and parallel triggering
• GitHub Actions — adds workflows for auto-backport, post-backport checklist, changelog sync, package docs validation, dashboard YAML validation, sweep workflows (field mapping conflicts, ingest pipeline safety, httpjson pagination, pipeline error handling, dashboard data scope), Vale linting, docs build/deploy/preview, and various trigger/patrol workflows
• Go tooling — cmd/backport sub-module with the full backport apply/changelog/checklist/inventory/owners/packages logic and its test suite; dev/ tooling additions (citools, coverage, packagenames, gitutil, scripts)
• Root module — go.mod/go.sum updates, magefile.go additions, .gitignore updates

GitHub Actions resolves workflow files from the branch where the event occurs, not from main. Backport-branch workflows (changelog sync, post-backport checklist, owner checks, auto-backport) must be present on the backport branch itself to fire correctly.

Proposed commit message

```
Sync CI configuration with main branch for backport-cloud_asset_inventory-1.4.

Keep CI pipelines, GitHub Actions, and tooling consistent between active backport
branches and `main`, so that automated backport workflows and tooling improvements
land on all supported branches.

WHY:
GitHub Actions resolves workflow files from the branch where the event occurs,
not from `main`. Backport-branch workflows (changelog sync, post-backport
checklist, owner checks, auto-backport) must be present on the backport branch
itself to fire correctly.
```

Author's Checklist

• CI configuration files have been synced verbatim from `main`.

Related issues

• Relates backport: deploy backport-branch automation workflows to active backport branches #19262

---

This PR was generated with the assistance of Claude (claude-sonnet-4-6).

🤖 Generated with Claude Code

[infra-vault-gh-plugin-prod]

💔 Build Failed

• Buildkite Build
• Commit: a95e4dc

Failed CI Steps

• Check integrations aws
• Check integrations aws_bedrock
• Check integrations aws_logs
• Check integrations canva
• Check integrations carbon_black_cloud
• Check integrations cisco_umbrella
• Check integrations cloudflare_logpush
• Check integrations crowdstrike
• Check integrations cyera
• Check integrations elastic_security
• Check integrations f5_bigip
• Check integrations github
• Check integrations imperva_cloud_waf
• Check integrations jamf_protect
• Check integrations netskope
• Check integrations php_fpm
• Check integrations qualys_vmdr
• Check integrations sentinel_one_cloud_funnel
• Check integrations servicenow
• Check integrations sublime_security
• Check integrations symantec_endpoint_security
• Check integrations system
• Check integrations tanium
• Check integrations trellix_edr_cloud

History

cc @mrodm

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

Package 1password 👍(2) 💚(0) 💔(1)

Expand to view

Data stream	Previous EPS	New EPS	Diff (%)	Result
signin_attempts	13333.33	10000	-3333.33 (-25%)	💔

To see the full report comment with /test benchmark fullreport

[Copilot]

Copilot wasn't able to review this pull request because it exceeds the maximum number of lines (20,000). Try reducing the number of changed lines and requesting a review from Copilot again.

[github-actions]

Changelog sync skipped — all changelog versions are already present on main.