camel-tui: Add run options form, properties editor, and F2 action improvements

[davsclaus]

Summary

• Run options form: Replace the simple name-only input with a multi-field form (Name, Port, cycling Max seconds/messages/idle, Dev, Observe, Backlog trace checkboxes)
• Properties editor: Second page in the run form showing editable application.properties from the selected example. Modified values passed as --prop=key=value. Press + to add custom properties
• Application properties: Add application.properties to bundled examples (timer-log, cron-log, rest-api, routes) using {{placeholder}} syntax
• Caption overlay: Ctrl+T or F2 menu to show typewriter-animated captions, supports multi-line via \n
• Classpath viewer: F2 menu to display parsed Maven GAV coordinates of running integration JARs
• Fuzzy filter: Reusable inline fuzzy search for list views (used in classpath popup)
• Doctor dialog: F2 menu for integration health checks
• Stop All: F2 menu to stop all running integrations
• Emoji icons: Visual icons for F2 action menu items

Test plan

• F2 → Run an example → press r → verify multi-field form with page navigation
• Tab to properties page → edit values → Enter → verify --prop= args in launched command
• Press + on properties page → add custom key:value → verify it's passed
• Space on Max field → cycles between seconds/messages/idle
• Ctrl+T → type caption → Enter → typewriter effect, hold, fade
• F2 → Show Classpath → verify JAR list with fuzzy filter
• F2 → Run Doctor → verify health check output
• F2 → Stop All → verify confirmation and stop

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

• dsl/camel-cli-connector
• dsl/camel-jbang/camel-jbang-core
• dsl/camel-jbang/camel-jbang-plugin-tui

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

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

💡 Manual integration tests recommended:

You modified dsl/camel-jbang/camel-jbang-core. The related integration tests in dsl/camel-jbang/camel-jbang-it are excluded from CI. Consider running them manually:

mvn verify -f dsl/camel-jbang/camel-jbang-it -Djbang-it-test

All tested modules (8 modules)

• Camel :: DSL :: CLI Connector
• Camel :: DSL :: CLI Debug
• Camel :: JBang :: Core
• Camel :: JBang :: MCP
• Camel :: JBang :: Plugin :: Route Parser
• Camel :: JBang :: Plugin :: TUI
• Camel :: JBang :: Plugin :: Validate
• Camel :: Launcher :: Container

---

⚙️ View full build and test results