Bump Keycloak version to 19.0.1

[sberyozkin]

I've spent nearly all day on this PR today as the new storage (Map based by default AFAIK) seems to have some clean up issues at the host and Dev Services based tests have been failing randomly (I've captured the same tests passing and then failing), and also the start time has increased, but then I've remembered that Pedro has advised to try --storage=chm - it stabilized it and the startup time is at least no worse compared to 18.0.2 on my old laptop but will likely be even better on newer laptops.
Also integration-tests/oidc-client-reactive which starts Dev Services for KC has a redundant profile.
I'm still seeing side-effects with 2 quickstarts but it looks like they are more related to the fact they use the realms created by very old Keycloak - I'll try to finalize it - but this PR itself should be ready for review.

[sberyozkin]

quarkusio/quarkus-quickstarts#1159 fixes the quickstart issues, but this PR needs to be merged first

[quarkus-bot]

Failing Jobs - Building 517c971

Status	Name	Step	Failures	Logs	Raw logs
✔️	JVM Tests - JDK 11
⌛	JVM Tests - JDK 11 Windows	Build	Failures	Logs	Raw logs
✔️	JVM Tests - JDK 17
✖	JVM Tests - JDK 18	Build	Failures	Logs	Raw logs

Full information is available in the Build summary check run.

Failures

⚙️ JVM Tests - JDK 11 Windows #

- Failing: extensions/grpc/deployment 
! Skipped: extensions/opentelemetry/opentelemetry-exporter-jaeger/deployment extensions/opentelemetry/opentelemetry-exporter-otlp/deployment extensions/opentelemetry/opentelemetry/deployment and 20 more

📦 extensions/grpc/deployment

✖ io.quarkus.grpc.server.devmode.GrpcDevModeTest.testEchoStreamReload - More details - Source on GitHub

java.util.concurrent.RejectedExecutionException
	at org.jboss.threads.RejectingExecutor.execute(RejectingExecutor.java:38)
	at org.jboss.threads.EnhancedQueueExecutor.rejectShutdown(EnhancedQueueExecutor.java:2076)

---

⚙️ JVM Tests - JDK 18 #

- Failing: integration-tests/micrometer-prometheus 

📦 integration-tests/micrometer-prometheus

✖ io.quarkus.it.micrometer.prometheus.ClientRequestTest.testClientRequests line 36 - More details - Source on GitHub

java.lang.AssertionError: 
1 expectation failed.
Response body doesn't match expectation.

[pedroigor]

@sberyozkin FYI, sessions do not expire after server restart if you are using storage=chm. That is because they are stored in the filesystem.

Not sure if it might impact tests that expect otherwise.

[sberyozkin]

Hi @pedroigor I thought I left a comment here but looks like I lost it, yeah, I just said I'd check it out with devservices - it has no side-effects, as even if we restart, it is a new container start, so for example, I logged in as admin:admin and then stopped Quarkus without logging out, and then returned to Dev UI and got a new authentication challenge. I guess it is more related to the case where Keycloak is started from the cmd with kc.sh which is not the case with the devservices.

So I'll go ahead and merge, thanks

[rsvoboda]

There are new failures in security related QS, see https://github.com/quarkusio/quarkus-quickstarts/actions/workflows/native-build-development.yml
These failures are related to this change, when I used quarkus main 52379a5ce2e7d61447d96f7cb9f9c133822788b6 (the one before the merge) QS was passing