github-actions: support flaky test triage

[v1v]

Proposed commit message

Triage automatically any issues created by elastic-vault-github-plugin-prod[bot]:

• [Flaky Test] github.com/elastic/beats/v7/x-pack/metricbeat/tests/integration TestMetricbeatOTelE2E #49827

Then we will work in the execution part

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
• I have added tests that prove my fix is effective or that my feature works. Where relevant, I have used the stresstest.sh script to run them under stress conditions and race detector to verify their stability.
• I have added an entry in ./changelog/fragments using the changelog tool.

Disruptive User Impact

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

[botelastic]

This pull request doesn't have a Team:<team> label.

[github-actions]

🤖 GitHub comments

Just comment with:

• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: d6a4e817-3a16-46f1-89ae-f5e2e834bfff

📥 Commits

Reviewing files that changed from the base of the PR and between 5b32798 and 2d25785.

📒 Files selected for processing (1)

• .github/workflows/trigger-issue-triage.yml

---

📝 Walkthrough

Walkthrough

A workflow configuration file was updated to pass an allowed-bot-users input parameter to a reusable upstream workflow. The input designates two bot identities as permitted users for the issue triage automation. This parameter addition extends the control options passed to the elastic/ai-github-actions workflow without modifying triggers, permissions, or secret handling.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

• 🛠️ Update Documentation: Commit on current branch
• 🛠️ Update Documentation: Create PR

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[fr4nc1sc0-r4m0n]

LGTM