chore(ci): add regen-push bot script and update commenter message

[gnodet]

What

Add etc/scripts/regen-push.sh — a standalone script that automatically pushes "Regen" commits to PR branches when CI detects uncommitted generated file changes.

Update pr-test-commenter.yml to inform contributors that a bot will auto-push the regen fix when maintainer edits are allowed, with manual instructions as fallback.

How it works

1. ETag-polls the GitHub Events API (free on 304 — no API quota consumed when idle)
2. When activity is detected, queries the Artifacts API for regen-patch artifacts
3. For each artifact: verifies the PR is still open, SHA matches (not stale), and maintainerCanModify=true
4. Downloads the patch, shallow-clones the PR branch (works for both same-repo and fork PRs), applies the patch, commits "Regen", pushes
5. Tracks pushed run IDs in a state file to avoid re-pushing

Requirements

• gh CLI authenticated with a maintainer PAT (repo scope)
• python3 (for JSON parsing)
• curl (for ETag polling)

Usage

# One-shot check
./etc/scripts/regen-push.sh

# Dry run (shows what would be pushed)
./etc/scripts/regen-push.sh --dry-run --verbose

# As a cron job (every 5 minutes)
*/5 * * * * /path/to/regen-push.sh --repo apache/camel

Commenter update

The PR comment posted by pr-test-commenter.yml now mentions that a bot will auto-push the fix when Allow edits from maintainers is enabled, with manual instructions as fallback.

[github-actions]

🌟 Thank you for your contribution to the Apache Camel project! 🌟
🤖 CI automation will test this PR automatically.

🐫 Apache Camel Committers, please review the following items:

• First-time contributors require MANUAL approval for the GitHub Actions to run
• You can use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot although they are normally detected and executed by CI.
• You can label PRs using skip-tests and test-dependents to fine-tune the checks executed by this PR.
• Build and test logs are available in the summary page. Only Apache Camel committers have access to the summary.

⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.

[github-actions]

✅ Generated files are up to date

An earlier CI run reported uncommitted generated changes; the latest run no longer does.

[github-actions]

🧪 CI tested the following changed modules:

• etc

---

🔬 Scalpel shadow comparison — Scalpel: 1 tested, 0 compile-only — current: 0 all tested

Maveniverse Scalpel detected 1 affected modules (current approach: 0).

⚠️ Modules only in Scalpel (1)

• camel-etc

Skip-tests mode would test 1 modules (1 direct + 0 downstream), skip tests for 0 (generated code, meta-modules)

Modules Scalpel would test (1)

• camel-etc

ℹ️ Shadow mode — Scalpel observes but does not affect test execution. Learn more

---

⚙️ View full build and test results