KnownDependenciesResolver to support packages

[bartoszpop]

This pull request enhances KnownDependenciesResolver to match the well known dependencies against packages up to the root package, so that a single entry in the camel-main-known-dependencies.properties file is sufficient to load any class from this jar, instead of having a separate entry for each class.

This is a cherry-pick from #17034

[davsclaus]

what is the reason for this, this file is maintained by camel project and not be end users. It is an implementation detail.

[davsclaus]

okay do you have an example of a real world situation this was beneficial - just want to understand better.

[bartoszpop]

Hi @davsclaus, thank you for your feedback. We utilize this mechanism to inject predefined bean and AggregationStrategy classes to JBang runtime, meaning that we pass the parameter --dep=com.example:custom-catalog:1.0.0 and is contains camel-main-known-dependencies.properties with a list of custom classes pointing to custom jars, e.g.

org.example.some.BeanClass=com.example:some-jar:1.0.0
org.example.some.AggregationStrategyClass=com.example:some-jar:1.0.0
org.example.other.BeanClass=com.example:other-jar:1.0.0

Instead of having separate entries for each class it would be reasonable to have them merged, because all classes in the same jar will share the same package, e.g.

org.example.some=com.example:some-jar:1.0.0
org.example.other=com.example:other-jar:1.0.0

[davsclaus]

You cannot keep dropping sub package names, which can end up into picking the wrong JAR.
It should only drop the classname

[bartoszpop]

But the class may be in a subpackage, e.g. consider com.example:somejar:1.0.0 and two classes com.example.somejar.subpackage.SomeClass
com.example.somejar.otherpackage.OtherClass