The Compose Dev Service discovers Compose files in a Quarkus project and starts services defined in the Compose project, using Docker Compose or Podman Compose.

Detailed feature docs in compose-dev-services.adoc.

Extension dev services build steps can consume the DevServicesComposeProjectBuildItem and can locate whether compose has created an eligible service that they can configure the Quarkus app for, much like how dev service instances shared between projects.

This change already integrates following platform dev services: Datasource Dev Services (DB2, MariaDB, MS SQL, MySQL, Oracle, Postgres), Keycloak, Elasticsearch, Infinispan, Kafka, Kubernetes, AMQP, MQTT, Pulsar, RabbitMQ, MongoDB, Observability, Redis, Apicurio Schema Registry.

For any not-yet-integrated service, it is possible to include description in the compose files to produce runtime configuration for the Quarkus application in dev/test.

The dev service hashes targeted compose files in order to detect changes in the content and restart compose.

Dev UI Devservices pane shows a brief description of the Compose Dev Services.

If a Quarkus project doesn't contain Compose files, it can still discover Compose services using a configuration, effectively sharing a single compose project between multiple projects.

As discussed in #46848, this changes dev service label values keycloak and lgtm