Allow finer tuning of shared network usage by Keycloak DevServices

[lbroudoux]

This PR follows up #39899 and is related to the issues encountered here: microcks/microcks-quarkus#48 and there: microcks/microcks-quarkus#49.

At the moment Keycloak OIDC DevServices systematically use the shared network if it exists - leading to inconsistencies if a shared network has been initialized for other needs (see discussion #38398).

Like we did for the database-related DevServices in #39899, we should be more subtle and clearly determine if joining a shared network is required (by the user, by integration test) so that DevServices can only join on purpose.

Signed-off-by: Laurent Broudoux laurent.broudoux@gmail.com

[quarkus-bot]

Thanks for your pull request!

Your pull request does not follow our editorial rules. Could you have a look?

• title should preferably start with an uppercase character (if it makes sense!)
• title should not start with chore/docs/feat/fix/refactor but be a proper sentence

_{This message is automatically generated by a bot.}

[geoand]

Thanks!

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit e4d746e.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.