Fix crash tracking initialization on Windows

[bmermet]

What Does This Do

This commit addresses UnsupportedOperationException errors when initializing crash tracking on Windows systems.

Motivation

Instrumenting a java app on Windows currently logs the following warnings:

[dd.trace 2025-11-27 09:52:09:269 +0000] [dd-task-scheduler] SEND_TELEMETRY datadog.crashtracking.Initializer - Unsupported permissions 'rwxrwxrwx' for C:\Users\Administrator\AppData\Local\Temp\ddprof_administrator\pid_488. Crash tracking will not work properly.
[dd.trace 2025-11-27 09:52:09:284 +0000] [dd-task-scheduler] SEND_TELEMETRY datadog.crashtracking.Initializer - Unexpected exception while initializing OOME notifier. OOMEs will not be tracked. [null] (Change the logging level to debug to see the full stacktrace)

Additional Notes

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: [PROJ-IDENT]

[amarziali]

LGTM. Thanks for the fix — that recurring log message can definitely be annoying for Windows users. For future improvements, we should handle this scenario more gracefully on Windows, since we may still need to set read permissions for everyone.

[PerfectSlayer]

🎯 suggestion: ‏Rather than disabling the RO / RW set, I would implement the Windows related calls:

DosFileAttributeView view = Files.getFileAttributeView(path, DosFileAttributeView.class);
view.setReadOnly(true);

I know it's early to give feedback as it's a draft, but I saw it was already approved 😅