Build time Kamelet processing may result in StackOverflowError

[jamesnetherton]

Bug description

To reproduce, include camel-kamelets and the following configuration:

quarkus.camel.kamelet.identifiers = aws-s3-sink

Seems there are other Kamelets in the catalog that also lead to the same issue.

Build step io.quarkus.deployment.steps.MainClassBuildStep#build threw an exception: java.lang.StackOverflowError
    at io.quarkus.deployment.recording.BytecodeRecorderImpl.loadComplexObject(BytecodeRecorderImpl.java:1064)
    at io.quarkus.deployment.recording.BytecodeRecorderImpl.loadObjectInstanceImpl(BytecodeRecorderImpl.java:914)
    at io.quarkus.deployment.recording.BytecodeRecorderImpl.loadObjectInstance(BytecodeRecorderImpl.java:586)
    at io.quarkus.deployment.recording.BytecodeRecorderImpl.loadComplexObject(BytecodeRecorderImpl.java:1361)
    at io.quarkus.deployment.recording.BytecodeRecorderImpl.loadObjectInstanceImpl(BytecodeRecorderImpl.java:914)
    at io.quarkus.deployment.recording.BytecodeRecorderImpl.loadObjectInstance(BytecodeRecorderImpl.java:586)
    at io.quarkus.deployment.recording.BytecodeRecorderImpl.loadComplexObject(BytecodeRecorderImpl.java:1361)

Unless we can fix this issue in a reliable way, such that we don't need to keep patching the build time code, then I propose to deprecate quarkus.camel.kamelet.identifiers and its associated build items etc. Runtime loading of Kamelets already works fine and is what JBang will push folks towards if they export an app to CQ.