Enable native heap dump monitoring by default

[galderz]

Closes #35729

[zakkak]

Looks good to me as long as start-up times and binary size are indeed minimally affected.

Have you tried passing heapdump explicitly through quarkus.native.monitoring? Is it okay to be added twice in the command line?

[quarkus-bot]

Failing Jobs - Building 8eceb71

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

Full information is available in the Build summary check run.

Failures

⚙️ JVM Tests - JDK 17 Windows #

- Failing: integration-tests/smallrye-context-propagation 

📦 integration-tests/smallrye-context-propagation

✖ io.quarkus.context.test.SimpleContextPropagationTest.testArcTCContextPropagationDisabled line 92 - More details - Source on GitHub

org.opentest4j.AssertionFailedError: expected: <2> but was: <3>
	at org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
	at org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)

[galderz]

Have you tried passing heapdump explicitly through quarkus.native.monitoring? Is it okay to be added twice in the command line?

It is fine. The distinct() stream call makes sure that we don't add the same monitoring option twice.

[gsmet]

I agree it looks like a better default if it doesn't cost us much.