fix(jbang): update container image-check to match renamed CLI version output

[oscerd]

Summary

• The Camel CLI version command output was renamed from Camel JBang version: to Camel CLI version:, but the container image-check Makefile target still used the old prefix in its sed pattern.
• Updated both the default check (line 100) and the per-arch check (line 106) to use the new Camel CLI version: prefix so the version extraction works correctly.

Test plan

• Run make CAMEL_VERSION=<version> image-check and verify it passes
• Run make CAMEL_VERSION=<version> images-check-all and verify all JDK/arch variants pass

Claude Code on behalf of oscerd

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 4.6 (1M context) noreply@anthropic.com

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

• dsl/camel-jbang

---

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

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

⚠️ Modules only in Scalpel (17)

• camel-jbang-console
• camel-jbang-core
• camel-jbang-it
• camel-jbang-main
• camel-jbang-mcp
• camel-jbang-parent
• camel-jbang-plugin-edit
• camel-jbang-plugin-generate
• camel-jbang-plugin-kubernetes
• camel-jbang-plugin-mcp
• camel-jbang-plugin-route-parser
• camel-jbang-plugin-test
• camel-jbang-plugin-tui
• camel-jbang-plugin-validate
• camel-launcher
• camel-launcher-container
• coverage

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

Modules Scalpel would test (8)

• camel-jbang-console
• camel-jbang-mcp
• camel-jbang-parent
• camel-jbang-plugin-mcp
• camel-jbang-plugin-route-parser
• camel-jbang-plugin-tui
• camel-jbang-plugin-validate
• camel-launcher-container

Modules with tests skipped (9)

• camel-jbang-core
• camel-jbang-it
• camel-jbang-main
• camel-jbang-plugin-edit
• camel-jbang-plugin-generate
• camel-jbang-plugin-kubernetes
• camel-jbang-plugin-test
• camel-launcher
• coverage

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

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

• dsl/camel-jbang: 11 test(s) disabled on GitHub Actions

All tested modules (17 modules)

• Camel :: Coverage
• Camel :: JBang :: Console
• Camel :: JBang :: Core
• Camel :: JBang :: Integration tests
• Camel :: JBang :: MCP
• Camel :: JBang :: Main
• Camel :: JBang :: Parent
• Camel :: JBang :: Plugin :: Edit
• Camel :: JBang :: Plugin :: Generate
• Camel :: JBang :: Plugin :: Kubernetes
• Camel :: JBang :: Plugin :: MCP
• Camel :: JBang :: Plugin :: Route Parser
• Camel :: JBang :: Plugin :: TUI
• Camel :: JBang :: Plugin :: Testing
• Camel :: JBang :: Plugin :: Validate
• Camel :: Launcher
• Camel :: Launcher :: Container

---

⚙️ View full build and test results