Use Data Type Transformer API provided by Camel 4.0

[christophd]

• Camel 4.0 introduces a data type support based on the transformer API. Use this instead of the interim implementation in utils
• Remove data type transformers that are now provided by Camel core
• Remove interim data type processor implementation in this repository and use data type processor implementation provided by Camel 4
• Refactor data type action Kamelet to use new Camel 4 data type processor
• Keep those data type transformer implementations (Avro, Json Struct, ...) that have not been ported to Camel core yet
• Update to YAKS 0.16.0 as it allows to explicitly set the camel-kamelets version in Camel JBang
• Update aws-ddb-sink Kamelet to use new data type transform API

[claudio4j]

The implementation and kamelets are more clear and concise to use.

[christophd]

YAY, tests are green!

@claudio4j thank you! Yes I really like the new way to use transform EIP in combination with data types:

from:
  uri: "kamelet:source"
  steps:
  - transform:
      to-type: "aws2-ddb:application-json"
  - to:
      uri: "aws2-ddb:{{table}}"

Also the built-in data type support on Kamelet source/sink makes it easy to use it in a pipe/binding:

kind: KameletBinding
metadata:
  name: aws-s3-to-http
spec:
  source:
    ref:
      kind: Kamelet
      apiVersion: camel.apache.org/v1alpha1
      name: aws-s3-source
    properties:
      # ...
    dataTypes:
      out:
        format: "aws2-s3:application-cloudevents"

[oscerd]

Thanks a lot.