Figure out how to maintain Camel components that bring too old or too many non-convergent dependencies

Here is the list of components where the issue occurs: https://github.com/apache/camel-quarkus/issues?q=is%3Aissue+%5Bdependency+hell%5D

I see two options:

A. Keep enforcing dependencyConvergence, but manage in the extension instead of our global BoM
B. Stop enforcing dependencyConvergence for the given extensions

Both options have some potential to worsen the ability of the given extensions to combine flawlessly with the rest of the ecosystem. I think that's fine as long as it is documented.

Other ideas?

Start with the components listed by the repository's “dependency hell” issue search and compare how dependencyConvergence is enforced through the global BoM. Evaluate managing convergence in each extension versus disabling it for affected extensions, and document the resulting ecosystem-compatibility trade-offs once an approach is chosen.

Written by the indexing model from the issue text.