Native build fails when the kamelet DelegatingSchemaResolver becomes reachable without camel-jackson

`camel-kamelet` ships `org.apache.camel.component.kamelet.utils.format.schema.DelegatingSchemaResolver`, which hard-references the schema resolvers of the *optional* `camel-jackson`, `camel-jackson-avro` and `camel-jackson-protobuf` dependencies.

When that class becomes reachable in a native build — e.g. an application combining `camel-quarkus-kamelet` with a scheduled batch polling consumer such as `file` — and any of those dependencies is absent, the GraalVM analysis fails:

```
UnresolvedElementException: Error loading a referenced type:
java.lang.NoClassDefFoundError: org/apache/camel/component/jackson/transform/JsonSchemaResolver
```

The existing kamelet integration tests never make the class reachable, so CI does not catch it.

_Claude Code on behalf of @JiriOndrusek_

Start with camel-kamelet's DelegatingSchemaResolver and the existing kamelet integration tests. Reproduce a native build using camel-quarkus-kamelet with a scheduled file polling consumer while the optional camel-jackson dependencies are absent. Done means the reachable class no longer causes GraalVM analysis to fail and the integration tests cover this scenario.

Written by the indexing model from the issue text.