Move Elasticsearch dev service to its own Maven module

[yrodiere]

Description

Dev services for databases all have their own module under extensions/devservices. Elasticsearch propbably should, as well.

Implementation ideas

No response

[quarkus-bot]

/cc @gsmet, @loicmathieu, @quarkusio/devtools

[yrodiere]

While we're at it, we could also be more consistent with dev services for databases when it comes to the default image.

Elasticsearch dev services use a version hardcoded in their configuration class:

quarkus/extensions/elasticsearch-rest-client-common/deployment/src/main/java/io/quarkus/elasticsearch/restclient/common/deployment/ElasticsearchDevServicesBuildTimeConfig.java

Line 32 in 31c2513

@ConfigItem(defaultValue = "docker.elastic.co/elasticsearch/elasticsearch:7.17.0")

This is odds with the more sophisticated solutions we have for relational datasources, which relies on a properties file using interpolation to inject Maven properties:

quarkus/extensions/devservices/postgresql/src/main/java/io/quarkus/devservices/postgresql/deployment/PostgresqlDevServicesProcessor.java

Line 72 in 36f8e56

.parse(imageName.orElseGet(() -> ConfigureUtil.getDefaultImageNameFor("postgresql")))

quarkus/extensions/devservices/postgresql/src/main/resources/postgresql-devservice.properties

Line 1 in b7fad49

default.image=${postgres.image}