Log level change to bridge sysout errors to logging framework

[renjth-81]

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.

• You can label PRs using build-all, build-dependents, 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.

[renjth-81]

We are deploying Camel JBang applications to k8s with Opentelemetry and Loki. If there is an error on startup, some of the camel logs are getting printed to System.err . These logs are not getting exported to Loki. Changing log level to error in this commit will help capture these logs.

I used the below integration yaml to recreate the scenario where an exception is printed to System.err and the pod will restart.

`

• route:
  id: route-94d2
  nodePrefixId: route-b8d
  from:
  id: from-968b
  uri: timer
  parameters:
  delay: "0"
  timerName: oneTimeTimer
  period: "2000"
  steps:
  - log1:
  message: ${body}
  `

[davsclaus]

the camel framework is on purpose as-is