Docs: mention camel-quarkus-main in the contributor guide

docs/modules/ROOT/pages/contributor-guide/create-new-extension.adoc

@@ -66,6 +66,13 @@ because the test project needs to get finished. You need to build `poms/bom` and
 9. Complete the integration test module under `integration-tests/foo-abc`. Make sure you test both the consumer and the
    producer of the component (if the component supports both). Make sure the tests are passing both in the JVM mode
    (`mvn test`) and in the native mode (`mvn verify -Pnative`).
++
+[TIP]
+====
+If your test application is going to be configured via `camel.component.*` properties, you need to add the
+`camel-quarkus-main` dependency to the test project. See the xref:user-guide/bootstrap.adoc[Bootstrap] section of
+the User guide for more details.
+====
 
 10. In case of problems, consult the https://quarkus.io/guides/extension-authors-guide[Quarkus extension author's guide],
    ask for help in the given GitHub issue or via https://gitter.im/apache/camel-quarkus[Camel Quarkus chat].

docs/modules/ROOT/pages/contributor-guide/promote-jvm-to-native.adoc

@@ -46,6 +46,13 @@ $ cd integration-tests/foo
 $ mvn clean verify -Pnative
 ----
 +
+[TIP]
+====
+If your test application is going to be configured via `camel.component.*` properties, you need to add the
+`camel-quarkus-main` dependency to the test project. See the xref:user-guide/bootstrap.adoc[Bootstrap] section of
+the User guide for more details.
+====
++
 Consider shifting some tasks from runtime to build time.
 The https://quarkus.io/guides/extension-authors-guide[Quarkus extension author's guide] may be a good ally for this.