ci: fix CamelJfrDevConsoleTest for the registered -> runtimeEvents status rename

[oscerd]

Problem

CamelJfrDevConsoleTest fails deterministically on main — 3 of its status tests (statusReportsNotRegisteredByDefault, statusReportsRegisteredWhenRuntimeInstrumentationEnabled, jsonStatusAndToggleReflectLiveState).

CamelJfrDevConsole renamed its status field from registered to runtimeEvents — both the TEXT line (sb.append("runtimeEvents: ")…) and the JSON key (root.put("runtimeEvents", …)), keeping the same isInstrumentationRegistered() value — but the test still asserted the old registered name (TEXT contains("registered: …") and JSON getBoolean("registered"), which now returns null).

Because camel-jfr is transitively pulled into the scalpel build of any PR that touches a core module, this was failing the CI of unrelated PRs.

Fix

Update the three assertions to the new runtimeEvents field name. Test-only, no production change. CamelJfrDevConsoleTest — 17 tests pass.

Claude Code on behalf of Andrea Cosentino (@oscerd).

🤖 Generated with Claude Code

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

• components/camel-jfr

---

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

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

Modules only in current approach (8)

• camel-jbang-mcp
• camel-jbang-plugin-mcp
• camel-jbang-plugin-route-parser
• camel-jbang-plugin-tui
• camel-jbang-plugin-validate
• camel-launcher-container
• camel-yaml-dsl-validator
• camel-yaml-dsl-validator-maven-plugin

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-jfr

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

All tested modules (9 modules)

• Camel :: JBang :: MCP
• Camel :: JBang :: Plugin :: MCP
• Camel :: JBang :: Plugin :: Route Parser
• Camel :: JBang :: Plugin :: TUI
• Camel :: JBang :: Plugin :: Validate
• Camel :: Java Flight Recorder
• Camel :: Launcher :: Container
• Camel :: YAML DSL :: Validator
• Camel :: YAML DSL :: Validator Maven Plugin

---

⚙️ View full build and test results