camel

Once an integration is built and the kit is available, kamel run --dev should start up really fast, in the order of seconds. E2E test should cover this scenario.

... and therefore our Geocoder test is failing when run with GOOGLE_API_KEY set.

Please see:
https://github.com/apache/camel-kafka-connector/blob/main/tooling/camel-kafka-connector-docs-maven-plugin/src/main/java/org/apache/camel/kafkaconnector/maven/docs/UpdateDocComponentsListMojo.java#L51
https://github.com/apache/camel-kafka-connector/blob/main/tooling/camel-kafka-connector-docs-maven-plugin/src/main/java/org/apache/camel/kafkaconnector/maven/docs/UpdateDocComponentsList

When <1>,<2>,... is used in docs there's some strange formatting between the labels and their descriptions.
For example in infinispan and knative.
There's different spacing between the labels and descriptions in each list:
![

for instance

<setBody id="setBody10">
--
<constant>
<![CDATA[
<v1:isAliveResponse xmlns:v1="http://model.ws.xxxx.com/global/v1">
<isAlive>true</isAlive>
</v1:isAliveResponse>
]]>
</constant>
</setBody>