There are situations where code outside our control needs to load classes/resources via the TCCL. One example of this is Jackson, which needs access to application classes as well as core SY serialization classes when serializing and deserializing a message. Unfortunately, we can't update Jackson to import these classes, so we must rely on the TCCL to include all classes used by Jackson during serialization. This is not an issue in EAP since our deployer wires necessary module dependencies into the deployment unit. We need a similar mechanism in Karaf.

NOTE: once this is implemented, we can revert the hacky changes which use DynamicImport inside of quickstarts with an SCA binding (camel-service, transform-json, transform-dozer).