Upgrade to Quarkus 3

[apupier]

Is your feature request related to a problem? Please describe.

Quarkus 3 has been released.

Describe the solution you'd like

Use Quarkus 3 instead of Quarkus 2

Describe alternatives you've considered

Additional context

A specific tooling is available to help for the migration https://quarkus.io/guides/update-to-quarkus-3

As additional to core changes, most probable main points are:

• move to Jakarta
• update graalvm image

[mkralik3]

PR https://github.com/KaotoIO/kaoto-backend/pull/695 , it contains:

• Kaoto-backend was upgraded to the latest Quarkus3 version (3.1.2)
• quarkus-universe-bom was changed to quarkus-bom because it is deprecated.
• kubernetes-client.devservices was disabled (which comes from quarkus-kubernetes-client and it is enabled by default) in tests where it is not used because it causes problems on Windows workflows due to uncatched exception from testcontainers package ( probable a bug, needs to be reported in Quarkus project )
• Changed imports for OpenTelemetry (@SpanAttribute @WithSpan) since they were moved to a different package and the original ones have been marked as deprecated
• Disabled OpenTelemetry by default since in Quarkus3 uses OpenTelemetry SDK Autoconfigure and expects OTLP exporter on localhost:4317 which causes SEVERE error in the log. Now, the users which wants to use kaoto-backend with some OTLP exporter (e.g. Jaeger), it can use quarkus config properties quarkus.otel.sdk.disabled=false and quarkus.otel.exporter.otlp.traces.endpoint=<OTLP gRPC receiver URL>
• CORS origins configuration property with Kaoto-ui URL needs to be set in production. For dev mode, all origins are allowed ( wildcard origins: /.*/ )