CAMEL-23353: Add configurable default Maven repos and dynamic Quarkus version resolution

[JiriOndrusek]

fixes https://issues.apache.org/jira/browse/CAMEL-23353

This PR adds two related enhancements for improved Maven repository handling and Quarkus platform
version resolution:

1. Configurable Default Maven Repositories: Adds support for extra default Maven repositories
   via classpath properties file (camel-extra-default-repos.properties) or system property
   (-Dcamel.extra.repos). This allows custom builds to embed repository configuration without
   requiring manual --repos flags.

2. Dynamic Quarkus Platform Version Resolution: Extends export --runtime quarkus and run --runtime quarkus to query the Quarkus platform registry for the latest compatible platform BOM
   version, matching the behavior of version list. Falls back to build-time version if registry is
   unavailable.

Testing

Following features were tested manually before PR was created:

• list quarkus versions java camel-launcher.jar version list --runtime quarkus --fresh:
  • both with and without -Dcamel.jbang.quarkus.platform.url=xxx
• export via java camel-launcher.jar export--runtime quarkus --logging --dir app Hello.java
  • I tested with the -Dcamel.extra.repos and -Dcamel.jbang.quarkus.platform.url
  • also negative scenario with -Dcamel.extra.repos and without -Dcamel.jbang.quarkus.platform.url which fails

Description

Target

• I checked that the commit is targeting the correct branch (Camel 4 uses the main branch)

Tracking

• If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

• I checked that each commit in the pull request has a meaningful subject line and body.

• I have run mvn clean install -DskipTests locally from root folder and I have committed all auto-generated changes.

[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/camel-jbang-core
• tooling/camel-tooling-maven

⚠️ 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 (7 modules)

• Camel :: JBang :: Core
• Camel :: JBang :: MCP
• Camel :: JBang :: Plugin :: Route Parser
• Camel :: JBang :: Plugin :: TUI
• Camel :: JBang :: Plugin :: Validate
• Camel :: Launcher :: Container
• Camel :: Tooling :: Maven

---

⚙️ View full build and test results

[davsclaus]

See comment in JIRA