CAMEL-20019: demo session handler implementation

[jono-morris]

Description

Draft code demonstrating a Vertx server handler implementation that manages server-side sessions and session cookie handling.

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.

[jono-morris]

Wondering whether this approach is what you're thinking in relation to this ticket, or whether you're hoping fore a more general cookie handler where cookies can be added/removed per route. The producer cookie handlers I found looked like they were for session handling.

[orpiske]

Probably this needs further review

[davsclaus]

Yeah a good start, this is vertx specific which of course works great as its vertx based.
Adding that camel cookie stuff is something you can look at after getting this vertx stuff implemented.
Also remember to add something into the docs, see src/main/docs folder