Deprecate kotlin extension

[jamesnetherton]

Rethinking my comments in #6438. I think we should deprecate (for 3.15.0) and remove camel-quarkus-kotlin (in whatever release we first integrate Camel 4.9.0) along with the kotlin-dsl extension.

I don't see any major benefits to keeping camel-quarkus-kotlin. All it does is provide a Kotlin function wrapper around RouteBuilder.configure.

If folks want to build with Kotlin then it's simple enough to add quarkus-kotlin and write a RouteBuilder impl.

class Routes : RouteBuilder() {
    override fun configure() {
        from("timer:tick?period=5s")
            .log("Hello World")
    }
}

[apupier]

Camel Quarkus 3.15 will be based on Camel 4.7?

camel-quarkus/pom.xml

Line 42 in 6260a42

<camel.major.minor>4.7</camel.major.minor> <!-- run after each change: cd docs && mvnd validate -->

Camel Quarkus 3.16 will be based on Camel 4.9? (or 4.8)?

Double-checking that I understand well and we can remove the Kotlin DSL part with Camel 4.9.

[jamesnetherton]

CQ 3.15.x will be LTS and will stay aligned to Camel 4.8.x
CQ 3.16.0 will probably be based on whatever the latest Camel 4.8.x release is. It depends if Camel 4.9.0 is available (unlikely TBH). So I guess we delay the extension removal until we integrate Camel 4.9.0.