Petals SE Camel

When a Petals exchange arrives on the Camel SE, its properties (not the message properties, that are business-specific but the exchange's) are copied to the Camel exchange. When a Camel exchange is sent to Petals, its properties (exchange's again) are copied to the newly sent Petals Exchange. There is thus a mixup with Flow Attributes, or CDK async property, etc. It is not possible to simply not forward them, because we actually don't know if some properties are not added explicitly by the route (for Camel exchanges sent to Petals), or if the properties set by another Petals service is needed in the route (for Petals exchanges sent received by Camel). It is not yet clear how to fix this.