Add profiling support for Quarkus native images

[jbachorik]

What Does This Do

Adds support for profiling in GraalVM native images built with Quarkus, and includes a smoke test to prevent regressions.

Changes:

1. Fix GraalVM native image build for profiler classes - Adds proper native-image configuration to defer profiler class initialization to runtime, fixing ClassNotFoundException: BufferWriter9 during Quarkus native builds
2. Use JMX for crashtracking in native images - Switches crashtracking initialization to use JMX in native image context
3. Add profiling smoke test for Quarkus native images - Extends the existing Quarkus native smoke test to validate profiling works correctly

Motivation

Issue #10446 reported that Quarkus native image builds failed with:

Error: Class initialization of com.datadoghq.profiler.ThreadContext failed
Caused by: java.lang.ClassNotFoundException: com.datadoghq.profiler.BufferWriter9

This occurred because GraalVM native-image performs class initialization at build time by default. Profiler classes like ThreadContext, BufferWriter, BufferWriter8, and BufferWriter9 depend on runtime state and must be deferred to runtime initialization.

The smoke test ensures:

• Native image builds successfully with profiling enabled (no ClassNotFoundException)
• Application starts without agent initialization errors
• Profiler produces JFR files with execution samples at runtime

Additional Notes

• The smoke test only runs with GraalVM (-PtestJvm=graalvm21)
• Test extends QuarkusSlf4jSmokeTest to reuse endpoint configuration
• Follows the same pattern as SpringBootNativeInstrumentationTest

Contributor Checklist

• Format the title according the contribution guidelines
• Assign the type: and (comp: or inst:) labels in addition to any useful labels
• Don't use close, fix or any linking keywords when referencing an issue.
  Use solves instead, and assign the PR milestone to the issue
• Update the CODEOWNERS file on source file addition, move, or deletion
• Update the public documentation in case of new configuration flag or behavior

Jira ticket: PROF-13580