CAMEL-24576: doc-sync 4.22 upgrade guide for dynamic-router backport

[davsclaus]

Doc-only follow-up required by the backport policy in CLAUDE.md: since #26011 backports the dynamic-router-control predicate gate (from #25992) to camel-4.22.x, the matching upgrade-guide entry needs to also exist on main's camel-4x-upgrade-guide-4_22.adoc (mirroring the existing pattern for other 4.22.0→4.22.1 patch-level security-hardening entries in that file, e.g. camel-exec, camel-ftp).

No code changes.

Claude Code on behalf of davsclaus

[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.

[gnodet]

Clean doc-sync PR that adds the dynamic-router upgrade-guide entry to the 4.22.0-to-4.22.1 section on main, as required by backport policy after PR #26011 backported the CAMEL-24576 code change to camel-4.22.x. Content is accurate, well-formatted, and follows the established pattern of other security-hardening entries in the same section.

Observations:

• Entry is well-written and accurately describes the security change from PR #25992 (allowPredicateFromMessage gate, insecure:dev annotation, predicateBean alternative, endpoint fallback, allowedSchemes option)
• AsciiDoc formatting follows project conventions — no explicit anchors before headings, proper code block syntax
• Placement is correct: under the 4.22.0→4.22.1 section, alphabetically consistent with existing entries

📋 PR Metadata

Aspect	Current	Suggested
Milestone	(none)	4.23.0

This review was generated by an AI agent and may contain inaccuracies. Please verify all suggestions before applying.

Claude Code on behalf of Guillaume Nodet

[github-actions]

🧪 CI tested the following changed modules:

• docs

---

🔬 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)

• docs

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

Modules Scalpel would test (1)

• docs

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

---

⚙️ View full build and test results