[Croway]

The Salesforce delete/update source Kamelets were corrected in #3078, but their checked-in packaged copies were left behind. The shipped JAR therefore still sets CamelSalesforceId, and the update sink removes the old sObjectId / sObjectName names.

Synchronize both packaged definitions with the corrected source templates, including the canonical JSONPath expressions and matching cleanup headers. Also replace kafka.TOPIC / kafka.TIMESTAMP in the HTTP router fixture with the application headers topic / timestamp; TimestampRouter reads those configured names and emits the current Camel Kafka override header. Application headers preserve the HTTP boundary, where Camel-internal headers are filtered.

This follows a review of the Camel 4.19–4.22.1 upgrade guides. The Salesforce change is already present on main; only the Kafka fixture cleanup applies there.

Validation:

• Full mvn verify passed (18 catalog unit tests).
• mvn verify -pl :camel-kamelets-itest -Denable.integration.tests -Dit.test=KafkaIT passed all 3 tests, including the HTTP-to-Kafka timestamp router.
• Documentation generator ran with no generated changes; Go catalog validator passed with no errors.
• git diff --check passed.

AI-generated by Codex on behalf of Federico Mariani.