Add containerId to DevServicesContent

[geoand]

For example, for mongo the property could look like:

quarkus.devservices.mongodb-client.containerId=someId

This info could then be used by tests that need to actually interact with the container itself in some way.

• Relates to: Add container's mapped ports to DevServicesContext.ContextAware::devServicesProperties #48963

[holly-cummins]

This may need an update to make sure containerId is populated for services on the new model (which, if so, we should do anyway, because otherwise it's a bug).

[geoand]

I actually realised that this solution only work with @QuarkusIntegrationTest which is definitely not great...

[geoand]

Looking at DevServiceDescriptionBuildItem, the ContainerInfo has all the info we need... @ozangunalp I think it makes sense to add that to DevServicesContext, WDYT?

It seems doable but would require touching plenty of things which I don't want to do while you and @holly-cummins are on the refactoring journey.

[ozangunalp]

Looking at DevServiceDescriptionBuildItem, the ContainerInfo has all the info we need... @ozangunalp I think it makes sense to add that to DevServicesContext, WDYT?

I agree, it seems reasonable to expose the container details through DevServicesContext. But let's wait for the advancement of WG - Dev Services Lifecycle.

I am kind of against exposing the containerId as config property. The info may be needed in tests or exposed ports can be mapped to config properties. but DevServicesAware implementors should do it.

[geoand]

Agreed to keep this on ice for now