Add DataTypeRegistry as bean in Camel context

[christophd]

Kamelets introduces a new concept for data types as described in #1980

At the moment each Kamelet adds a local bean representing the DataTypeRegistry in order to resolve converter implementations at runtime.

The registry for data type converters should be added to the Camel context as a singleton service. This can be done by adding quarkus.camel.service.registry.include-patterns property on the camel-quarkus project that builds the integration jars.

This way we avoid each Kamelet to introduce the local bean but reuse the singleton service. We would need to set this for KameletBinding or when an integration uses Kamelet components. Kamelets assume the DataTypeRegistry to be set on the CamelContext.

See apache/camel-kamelets#1162 for details

[github-actions]

This issue has been automatically marked as stale due to 90 days of inactivity.
It will be closed if no further activity occurs within 15 days.
If you think that’s incorrect or the issue should never stale, please simply write any comment.
Thanks for your contributions!

[christophd]

this one has become obsolete as the data type registry functionality has been moved to Camel core project. In Camel core project the registry is already exposed as a singleton bean on the Camel context by default.