CAMEL-20596: Propagate Azure Service Bus message headers

[dylanpiergies]

Description

Service Bus message application properties (a.k.a. custom headers) are now propagated to/from the Camel message, with the option to use a custom HeaderFilterStrategy.

Propagation of message headers is necessary to enable trace context propagation to work.

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)

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.

[oscerd]

This needs to be done on main branch. Then we can eventually backport to 4.4.x

[davsclaus]

okay I manually merged this for main branch so we can have this for 4.5.0

[dylanpiergies]

This needs to be done on main branch. Then we can eventually backport to 4.4.x

OK, I'll ensure I target main and then backport in any future PRs.