Bump camel.version from 4.1.0 to 4.2.0

Bumps `camel.version` from 4.1.0 to 4.2.0.

Updates `org.apache.camel:camel-catalog` from 4.1.0 to 4.2.0

Updates `org.apache.camel:camel-catalog-maven` from 4.1.0 to 4.2.0

Updates `org.apache.camel.springboot:camel-catalog-provider-springboot`
from 4.1.0 to 4.2.0

Updates `org.apache.camel:camel-route-parser` from 4.1.0 to 4.2.0

adapt test to updated description in catalog

---
updated-dependencies:
- dependency-name: org.apache.camel:camel-catalog
  dependency-type: direct:production
  update-type: version-update:semver-minor
- dependency-name: org.apache.camel:camel-catalog-maven
  dependency-type: direct:production
  update-type: version-update:semver-minor
- dependency-name:
org.apache.camel.springboot:camel-catalog-provider-springboot
  dependency-type: direct:production
  update-type: version-update:semver-minor
- dependency-name: org.apache.camel:camel-route-parser
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>

pom.xml

@@ -48,7 +48,7 @@
 		<junit.version>5.10.1</junit.version>
 		<assertj.version>3.24.2</assertj.version>
 		<jgit.version>6.7.0.202309050840-r</jgit.version>
-		<camel.version>4.1.0</camel.version>
+		<camel.version>4.2.0</camel.version>
 		<camel.kamelet.catalog.version>4.1.0</camel.kamelet.catalog.version>
 		<camel.quarkus.version>3.5.0</camel.quarkus.version>
 		<roaster.version>2.29.0.Final</roaster.version>

src/test/java/com/github/cameltooling/lsp/internal/completion/modeline/CamelKModelineCamelComponentPropertyTest.java

@@ -123,7 +123,7 @@ void testProvideCompletionForComponentAttribute() throws Exception {
 		List<CompletionItem> completionItems = completions.get().getLeft();
 		assertThat(completionItems).hasSize(3);
 		CompletionItem timerCompletionItem = completionItems.stream().filter(completionItem -> "bridgeErrorHandler".equals(completionItem.getLabel())).findFirst().get();
-		assertThat(timerCompletionItem.getDocumentation().getLeft()).isEqualTo("Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored.");
+		assertThat(timerCompletionItem.getDocumentation().getLeft()).isEqualTo("Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored.");
 	}
 
 	@Test
@@ -135,7 +135,7 @@ void testProvideCompletionForComponentAttributeWithDashedNotation() throws Excep
 		List<CompletionItem> completionItems = completions.get().getLeft();
 		assertThat(completionItems).hasSize(3);
 		CompletionItem timerCompletionItem = completionItems.stream().filter(completionItem -> "bridge-error-handler".equals(completionItem.getLabel())).findFirst().get();
-		assertThat(timerCompletionItem.getDocumentation().getLeft()).isEqualTo("Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored.");
+		assertThat(timerCompletionItem.getDocumentation().getLeft()).isEqualTo("Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored.");
 	}
 
 	@Test