Remove deprecated usage of Exchange.getOut in StaxProcessor

[apupier]

Description

Target

• I checked that the commit is targeting the correct branch (note that Camel 3 uses camel-3.x, whereas 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 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.

[davsclaus]

this is not correct, the old code is correct

Otherwise all the code should just be

exchange.getMessage().setBody

to only change the body, and not copy over headers etc.

[apupier]

By what should it be replaced then? How to get rid of the deprecated method?

[davsclaus]

By what should it be replaced then? How to get rid of the deprecated method?

Leave it as-is. The deprecation is for end users to not use it.
We will later in Camel 5 remove and change internal inside camel