Avoid hardcoded versions of catalogs

[davsclaus]

The lsp-server has a hardcoded dependency on the following dependencies

                <exclusion>
                    <groupId>org.apache.camel.kamelets</groupId>
                    <artifactId>camel-kamelets-catalog</artifactId>
                </exclusion>
                <exclusion>
                    <groupId>org.apache.camel.springboot</groupId>
                    <artifactId>camel-catalog-provider-springboot</artifactId>
                </exclusion>
                <exclusion>
                    <groupId>org.apache.camel.quarkus</groupId>
                    <artifactId>camel-quarkus-catalog</artifactId>
                </exclusion>

It may be better to make the camel-lsp-server more dynamic and allow to download a different versions so end users can use the correct version.

The current code is hardcoded and load default katalogs in their constructors which causes problems.
It would be good to make this more dynamic and plugin/controllable so we can provide existing loaded catalogs.

For example from other tools like Kaoto and Camel JBang.
https://issues.apache.org/jira/browse/CAMEL-22590

[davsclaus]

For example the CamelTextDocumentService has a KameletsCatalogManager which is not possible to update to another version. The should be an updateCamelKatalog method that does this.

Also since they load the default version in their constructors, there is no way to start with another version (the correct version) and avoid loading the embedded default version. (more nice to have)

[davsclaus]

With camel jbang edit, then you have errors like this

~/workspace/deleteme ❯ camel edit ddd.java                                                                                                                            1m 2s
Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/camel/kamelets/catalog/KameletsCatalog
	at com.github.cameltooling.lsp.internal.catalog.util.KameletsCatalogManager.<init>(KameletsCatalogManager.java:26)
	at com.github.cameltooling.lsp.internal.CamelTextDocumentService.<init>(CamelTextDocumentService.java:104)
	at org.apache.camel.dsl.jbang.core.commands.edit.CamelNanoLspEditor$LocalCamelDocumentService.<init>(CamelNanoLspEditor.java:194)
	at org.apache.camel.dsl.jbang.core.commands.edit.CamelNanoLspEditor.<init>(CamelNanoLspEditor.java:66)
	at org.apache.camel.dsl.jbang.core.commands.edit.EditCommand.doCall(EditCommand.java:70)
	at org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:71)
	at org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:37)
	at picocli.CommandLine.executeUserObject(CommandLine.java:2031)
	at picocli.CommandLine.access$1500(CommandLine.java:148)
	at picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2469)
	at picocli.CommandLine$RunLast.handle(CommandLine.java:2461)
	at picocli.CommandLine$RunLast.handle(CommandLine.java:2423)
	at picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2277)
	at picocli.CommandLine$RunLast.execute(CommandLine.java:2425)
	at picocli.CommandLine.execute(CommandLine.java:2174)
	at org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:205)
	at org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:72)
	at main.CamelJBang.main(CamelJBang.java:36)
Caused by: java.lang.ClassNotFoundException: org.apache.camel.kamelets.catalog.KameletsCatalog
	at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:445)
	at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:593)
	at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:526)

Due to those hardcoded dependencies, which is created during constructors which causes the JVM to load the class via its boot classloaded, and that is not flexible. You cannot provide a custom classloader, or any other way to avoid this.