Embed more Camel Catalog versions by default

[apupier]

Please describe the feature that you want to propose

Currently there is only latest community version.

I think we should have:

• latest community version at time of release
• latest LTS community version at time of release
• Red Hat supported versions

[lordrip]

Putting it on hold as we need the --json output from the Camel CLI

[apupier]

I think it would be better to have the list manually maintained. If using an automated way, if there is a release of Camel right before the Kaoto release it will pick it without further testing.
It also ensures reproducible build and to eb able to have a trace in the changelog.

[apupier]

would be convenient to have #1597 fixed to implement this one. But there is a workaround by providing a settings;xml with Red Hat Maven repository.
this can (I think) be done in the GitHub Actions directly https://github.com/actions/setup-java?tab=readme-ov-file#maven-options. otherwise other options/
* pass the parameters on command-line in github workflow
* commit a settings.xml to use during build

EDIT: #1597 has been fixed so no need to customize anything

[apupier]

I do not find find where/how the catalog is generated. Seems currently like the version picked depends on the version defined as dependency in the pom.xml currently, this is not parameters provided somewhere else

edit: I guess it is here

kaoto/packages/catalog-generator/package.json

Lines 22 to 23 in 11a04f5

	"build:default:catalog": "yarn run build:mvn; java -jar ./target/catalog-generator-0.0.1-SNAPSHOT.jar -o ./dist/camel-catalog -n \"Default Kaoto catalog\"",
	"build:ts": "node --loader ts-node/esm ./scripts/json-schema-to-typescript.mts",

[lordrip]

Yes, is exactly there, we pick whatever is defined in the pom.xml