Avoid calling getModifiers to remove DOMSerializer leak

[galderz]

A workaround to avoid #37498.

Avoiding to call Constructor.getModifiers removes leaking DOMSerializer as entry point and therefore does not bring in XML baggage.

See oracle/graal#8019 for details and updates on if/how upstream will fix this.

[galderz]

Converting this to draft for now, pending a decision on whether this will be fixed upstream.

[quarkus-bot]

Failing Jobs - Building bc77950

Status	Name	Step	Failures	Logs	Raw logs	Build scan
✖	JVM Tests - JDK 17	Build	Failures	Logs	Raw logs	🚧
✔️	JVM Tests - JDK 21					🚧
✖	Native Tests - Misc4	Build	Failures	Logs	Raw logs	🚧

Full information is available in the Build summary check run.

Failures

⚙️ JVM Tests - JDK 17 #

- Failing: extensions/resteasy-reactive/rest-client-reactive/deployment 
! Skipped: extensions/keycloak-admin-client-reactive/deployment extensions/micrometer-registry-prometheus/deployment extensions/micrometer/deployment and 36 more

📦 extensions/resteasy-reactive/rest-client-reactive/deployment

✖ io.quarkus.rest.client.reactive.StreamJsonTest.shouldReadUpToThreeTicks line 129 - More details - Source on GitHub

java.lang.AssertionError: Expected 3 items.  Only 3 items have been received.
	at io.smallrye.mutiny.helpers.test.AssertSubscriber.awaitItemEvents(AssertSubscriber.java:676)
	at io.smallrye.mutiny.helpers.test.AssertSubscriber.awaitItems(AssertSubscriber.java:440)

---

⚙️ Native Tests - Misc4 #

- Failing: integration-tests/opentelemetry-jdbc-instrumentation 

📦 integration-tests/opentelemetry-jdbc-instrumentation

✖ Failed to execute goal io.fabric8:docker-maven-plugin:0.43.4:start (docker-start) on project quarkus-integration-test-opentelemetry-jdbc-instrumentation: I/O Error

[yrodiere]

@galderz Thanks for working on this. I see oracle/graal#8041 was merged and supposedly fixes the problem; do you still want to merge this workaround or should we just wait for the fix to be included in a release of GraalVM?

[galderz]

Tested it locally and it looks fixed so closing this. No need for a workaround because this only affects unreleased GraalVM.