CAMEL-23533: ErrorRegistry - capture rich exchange snapshots

[davsclaus]

Summary

• Replaces ErrorRegistryEntry with BacklogErrorEventMessage extending a new shared BacklogEventMessage base interface (shared with BacklogTracerEventMessage)
• Error snapshots now capture detached exchange data (body, headers, properties, variables), message history, route group, endpoint URI, processing thread, and the full exception
• Configuration moves from camel.main.errorRegistry* to a dedicated camel.errorRegistry.* property group with expanded options (bodyMaxChars, bodyIncludeStreams, bodyIncludeFiles, includeExchangeProperties, includeExchangeVariables)
• Updated dev console, JMX MBean, tooling plugin, catalog, and documentation

Test plan

• ErrorRegistryTest passes — verifies error capture, snapshot data, TTL eviction, max entries, route scoping
• All changed modules compile cleanly
• Generated metadata and catalog files regenerated with correct camel.errorRegistry.* prefix

🤖 Generated with Claude Code on behalf of Claus Ibsen

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

🧪 CI tested the following changed modules:

• catalog/camel-catalog
• core/camel-api
• core/camel-base-engine
• core/camel-console
• core/camel-core
• core/camel-main
• core/camel-management-api
• core/camel-management
• docs
• tooling/maven/camel-package-maven-plugin

ℹ️ Dependent modules were not tested because the total number of affected modules exceeded the threshold (50). Use the test-dependents label to force testing all dependents.

⚠️ Some tests are disabled on GitHub Actions (@DisabledIfSystemProperty(named = "ci.env.name")) and require manual verification:

• core/camel-core: 2 test(s) disabled on GitHub Actions

Build reactor — dependencies compiled but only changed modules were tested (10 modules)

• Camel :: API
• Camel :: Base Engine
• Camel :: Catalog :: Camel Catalog
• Camel :: Console
• Camel :: Core
• Camel :: Docs
• Camel :: Main
• Camel :: Management
• Camel :: Management API
• Camel :: Maven Plugins :: Camel Maven Package

---

⚙️ View full build and test results