Sanitize RESTEasy Reactive exception logging

[geoand]

The PR does a few things:

• Adds debug logging for WebApplicationException instances
• Eliminates duplicate logging of exceptions
• Adds a hack to ensure that application provided IOException cases are logged properly

Closes: #31945

[quarkus-bot]

Failing Jobs - Building b40b179

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

Full information is available in the Build summary check run.

Failures

⚙️ Gradle Tests - JDK 11 Windows #

📦 integration-tests/gradle

✖ io.quarkus.gradle.devmode.AnnotationProcessorSimpleModuleDevModeTest.main line 13 - More details - Source on GitHub

org.awaitility.core.ConditionTimeoutException: Condition with lambda expression in io.quarkus.test.devmode.util.DevModeTestUtils that uses java.util.function.Supplier, java.util.function.Supplierjava.util.concurrent.atomic.AtomicReference, java.util.concurrent.atomic.AtomicReferencejava.lang.String, java.lang.Stringboolean was not fulfilled within 1 minutes.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:78)

---

⚙️ JVM Tests - JDK 17 Windows #

- Failing: extensions/grpc/deployment 
! Skipped: extensions/micrometer-registry-prometheus/deployment extensions/micrometer/deployment extensions/opentelemetry/deployment and 33 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:2136)

[Sgitario]

So, you're translating an IOException raised from either an InvocationHandler or an ResourceRequestFilterHandler to wrap the IOException into a UncheckedIOException, so QuarkusErrorHandler can handle it correctly, right?

Not sure if we can throw directly the UncheckedIOException exception (tho this is not very user-friendly), or fix it directly in QuarkusErrorHandler.

[geoand]

So, you're translating an IOException raised from either an InvocationHandler or an ResourceRequestFilterHandler to wrap the IOException into a UncheckedIOException, so QuarkusErrorHandler can handle it correctly, right?

Exactly, it's a total hack...

[geoand]

or fix it directly in QuarkusErrorHandler.

We can't really, because real IOException happen all the time due to clients closing connections prematurely.