chore(e2e): prepare languages deprecation

It will be driven by the runtime setting though.

docs/modules/ROOT/nav.adoc

@@ -28,9 +28,6 @@
 ** xref:languages/yaml.adoc[YAML]
 ** xref:languages/xml.adoc[XML]
 ** xref:languages/groovy.adoc[Groovy]
-** xref:languages/javascript.adoc[Javascript]
-** xref:languages/jsh.adoc[JSheel]
-** xref:languages/kotlin.adoc[Kotlin]
 * xref:configuration/configuration.adoc[Configuration]
 ** xref:configuration/dependencies.adoc[Dependencies]
 ** xref:configuration/build-time-properties.adoc[Build time properties]

docs/modules/ROOT/pages/languages/languages.adoc

@@ -12,9 +12,6 @@ Camel K supports multiple languages for writing integrations:
 | xref:languages/xml.adoc[XML]                  | Integrations written in plain XML DSL are supported (Spring XML with <beans> or Blueprint XML with <blueprint> not supported)
 | xref:languages/yaml.adoc[YAML]                | Integrations written in YAML DSL are supported
 | xref:languages/groovy.adoc[Groovy]            | Groovy `.groovy` files are supported (experimental)
-| xref:languages/kotlin.adoc[Kotlin]            | Kotlin Script `.kts` files are supported (experimental)
-| xref:languages/jsh.adoc[JShell]               | JShell (Java Shell) `.jsh` files are supported (experimental)
-| xref:languages/javascript.adoc[JavaScript]    | JavaScript `.js` files are supported (experimental)
 |=======================
 
 More information about each language is located in the language specific sections. Mind that the compatibility of each DSL with Camel will depend on the runtime you'll use to run the Integration.

docs/modules/ROOT/pages/troubleshooting/debugging.adoc

@@ -42,7 +42,7 @@ As you can see in the logs, the CLI has configured the integration in debug mode
 
 The JVM is suspended and waits for a debugger to attach by default: this behavior can be turned off using the `--suspend=false` option.
 
-Last thing to do is, to start a remote debugger on `localhost:5005` with the **integration file (if using Java, Groovy or Kotlin), the Apache Camel project, or the Camel K Runtime project**, opened on your IDE.
+Last thing to do is, to start a remote debugger on `localhost:5005` with the **integration file, the Apache Camel project, or the Camel K Runtime project**, opened on your IDE.
 
 The following picture shows the configuration of a remote debugger in IntelliJ IDEA:
 

e2e/native/files/Kotlin.kts → e2e/common/languages/files/PolyglotJava.java

@@ -15,7 +15,14 @@
  * limitations under the License.
  */
 
-from("timer:tick")
-  .setHeader("m").constant("string!")
-  .setBody().simple("Magic\${header.m}")
-  .log("Kotlin \${body}");
+import org.apache.camel.builder.RouteBuilder;
+
+public class PolyglotJava extends RouteBuilder {
+  @Override
+  public void configure() throws Exception {
+	  from("timer:tick")
+	  .setHeader("m").constant("java")
+	  .setBody().simple("Magicpolyglot-${header.m}")
+      .log("${body}");
+  }
+}