Disable unowned AI GitHub Actions workflows

[kcreddy]

Proposed commit message

ci: disable unowned AI GitHub Actions workflows

The sweep-* and trigger-* workflows wrap reusable workflows from
elastic/ai-github-actions. They were set up by a contributor who has
since left, and no team currently owns them.

Left running unowned, they generate noise that no one is triaging:
100+ AI-authored issues opened since March with no team labels, issues
filed against deprecated integrations, and issues created when the bots
themselves error out. Disable them to stop the noise until ownership is
decided — rather than deleting them, since deletion would lose the
config and history and a team may want to adopt and re-enable them.

Disable via a source-level `if: false` on the `run` job (not the
Actions UI toggle) so that re-enabling requires a reviewed PR and is
visible in git history — a silent flip-back-on isn't possible.

Disabled 16 workflows:
  sweep-dashboard-data-scope, sweep-field-mapping-conflicts,
  sweep-httpjson-pagination, sweep-ingest-pipeline-safety,
  sweep-pipeline-error-handling, trigger-breaking-change-detector,
  trigger-bug-hunter, trigger-docs-patrol,
  trigger-duplicate-issue-detector, trigger-issue-triage,
  trigger-mention-in-issue, trigger-mention-in-pr,
  trigger-newbie-contributor-patrol, trigger-pr-review,
  trigger-text-auditor, trigger-stale-issues

For the 12 single-job workflows, `if: false` plus a comment was added
directly to the `run` job.

For the 4 workflows that already had an `if:` activation condition
(trigger-issue-triage, trigger-mention-in-issue, trigger-mention-in-pr,
trigger-pr-review), YAML permits only one `if:` key per job, so the
original condition was moved into a comment above the job and replaced
with `if: false`. The comment preserves the exact original expression
so it can be restored verbatim on re-enable.

Excluded (intentionally not disabled):
  - trigger-package-tests-security-ml: actively maintained by the
    security-ml team (and uses elastic/ci-gh-actions, not
    elastic/ai-github-actions).
  - trigger-pr-actions-detective: has an extra step-level job
    (actions/github-script) before the reusable-workflow call, so it
    needs separate handling rather than a blanket if: false.

Note: workflows still trigger on their existing events/schedules but
the job is skipped, producing empty "skipped" runs. This is the
accepted trade-off for keeping the disabled state in source.

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices

[infra-vault-gh-plugin-prod]

Pinging @elastic/ecosystem (Team:Ecosystem)

[mrodm]

We (@elastic/ecosystem) did not add those agent workflows. Adding as a reviewers @v1v and @theletterf in case they know about these workflows.