We should make the build system generate camel component json metadata with nested configuration options, like we do for endpoints.
For example some components allow to set a global configuration class which is then copied and then per endpoint can override individual settings. This class is annotated with @UriParams and the metadata tool generate these options included for endpoint.
For component we only refer to the configuration class itself and not its options.
Then the options table in the generated docs should also be updated for components to be more similar to what we do for SB, eg with camel.component.kafka.xxx as prefix. Then its the same way to configure this with SB, Main, Quarkus, Kafka Connectors and whatnot. And for Java configuration you still have just java code. Also the componentdsl tool needs to be updated to support this.