[CAMEL-18276] : azure-service-bus component support for session enabled entities

[Pulin412]

Description

Session support for azure-service-bus component. Existing component is updated to handle both non-session (existing functionality) and session based entities.

New properties are added -

• sessionId - For producer, sessionId is required to send with message while publishing message for session based entities.
• sessionEnabled - For consumer, boolean flag to let the consumer create Session aware clients to consume messages from session aware entities.

JIRA Issue - https://issues.apache.org/jira/browse/CAMEL-18276

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.

[oscerd]

Looks good, I'd like to have feedback from @dylanpiergies and @davsclaus

[davsclaus]

I wonder if sessionEnabled should be an option on component level, so you can configure this once if you always want to use this. And if so you are welcome to work on that for another PR

[dylanpiergies]

Seems OK to me. I've double checked the integration tests are passing, since they don't run during builds. All good. Aside from that, I haven't really delved into the nuts and bolts of the session functionality with Service Bus. I'd have to spend some time looking through the Azure documentation to see if there are any additions that need to be made for full-featured session support.