Queue the log messages if the queue compaction leads to new space

[jaikiran]

Fixes #19381

As rightly noticed and debugged by the reporter in the linked issue, the QuarkusDelayedHandler has a return statement which prevents the log message(s) from being queued after a queue compaction has made available new space. This commit fixes that issue.

[quarkus-bot]

Failing Jobs - Building c039d16

Status	Name	Step	Test failures	Logs	Raw logs
✖	JVM Tests - JDK 11	Build	Test failures	Logs	Raw logs
✔️	JVM Tests - JDK 16

Full information is available in the Build summary check run.

Test Failures

⚙️ JVM Tests - JDK 11 #

📦 extensions/smallrye-reactive-messaging-kafka/deployment

✖ io.quarkus.smallrye.reactivemessaging.kafka.deployment.testing.KafkaDevServicesContinuousTestingTestCase.testContinuousTestingScenario2 - More details - Source on GitHub

java.lang.RuntimeException: 
java.lang.RuntimeException: java.lang.RuntimeException: java.lang.RuntimeException: java.lang.RuntimeException: java.lang.RuntimeException: io.quarkus.builder.BuildException: Build failure: Build failed due to errors
	[error]: Build step io.quarkus.kafka.client.deployment.DevServicesKafkaProcessor#startKafkaDevService threw an exception: org.testcontainers.containers.ContainerLaunchException: Container startup failed
	at org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:330)
	at org.testcontainers.containers.GenericContainer.start(GenericContainer.java:311)
	at io.quarkus.kafka.client.deployment.DevServicesKafkaProcessor.lambda$startKafka$6(DevServicesKafkaProcessor.java:224)
	at java.base/java.util.Optional.orElseGet(Optional.java:369)
	at io.quarkus.kafka.client.deployment.DevServicesKafkaProcessor.startKafka(DevServicesKafkaProcessor.java:232)
	at io.quarkus.kafka.client.deployment.DevServicesKafkaProcessor.startKafkaDevServ...

[gsmet]

Thanks! Glad to have you back :).