Embed catalog for provided Camel version

it will avoid to use Ivy/groovy which is causing a lot of trouble of performance and stability.

technical:

• use of "normal" DefaultCamelCatalog without a MavenVersionManager and use the version available on the classpath
• will require a different plugin for each version

this is just what was proposed and not retain when working on the decoupling of camel version

• pros:
  • stability inimproved for most common use case
  • performance improved for most common use case
• cons:
  • more maintenance
  • increase size of Fuse Tooling