custom components are not affected by camel version changes

Currently users of the tooling are allowed to switch the used camel version. As the camel version change only works for specific Maven coordinates automatically custom components are not affected by the change because the use different GAV coordinates than default camel dependencies do.

That probably applies to all custom camel components done by 3rd party entities. (AMQ, SAP, ...)

We need to find a way to let the extension point user for the palette items know about Camel version changes and then given them the chance to react on it...either by giving them access to the pom.xml and/or modifying the result of the getDependencies() method call.