JVM Crash on Windows 11 24H2 with SentinelOne installed

Let's make sure issue is not already fixed in latest builds first.

- [x] I verified I can reproduce this issue against [latest Integration Build of Eclipse SDK](https://download.eclipse.org/eclipse/downloads/)

## Steps to reproduce

On Windows 11, version 24H2, users who have SentinelOne security software installed experience a JVM crash at startup when launching Eclipse (observed in both Eclipse 4.31 and 4.35).
The crash does not occur if SentinelOne is uninstalled or if the Eclipse executables and JVM are explicitly whitelisted in SentinelOne.

From a fresh installation and clean workspace:

- Install Windows 11, version 24H2
- Install SentinelOne security software
- Attempt to launch Eclipse 4.35 → JVM crash
(Without SentinelOne: Eclipse launches successfully)

I tried

Whitelisting is not a viable long-term solution, as it exposes users to potential risks when installing third-party plugins.

I expected: The IDE to launch on Windows 11 24H2 that has SentinelOne installed.

But got: IDE crashes when attempting to launch.

## Here is some relevant log output

The Windows Event Log consistently reports a crash involving ntdll.dll (32-bit):
```
Sig[3].Name=Fault Module Name
Sig[3].Value=ntdll.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=10.0.26100.2454
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=7cb6b6a8
Sig[6].Name=Exception Code
Sig[6].Value=c00000fd
Sig[7].Name=Exception Offset
Sig[7].Value=0000000000163df7
```


Stack traces point to callback functions bound to the 32-bit ntdll.dll, suspected to originate from the 32-bit Eclipse launcher on a 64-bit OS.

A related SentinelLabs post from 2020 recommends avoiding reliance on the 32-bit ntdll.dll: https://www.sentinelone.com/labs/case-study-why-you-shouldnt-trust-ntdll-from-kernel-image-load-callbacks/

Additionally, it appears the Windows GUID for version 24H2 is missing in the Eclipse launcher source code, though this may or may not be directly related.

We recommend evaluate updating the Eclipse launcher to avoid binding to 32-bit ntdll.dll on 64-bit systems.

Alternatively, engage with Microsoft to possibly issue a Block Update for Windows 11 24H2 until the root cause is clarified: https://learn.microsoft.com/en-us/windows/release-health/status-windows-11-24h2

## Tested under this environment:
* OS & version: Windows 11 24H2
* Eclipse IDE/Platform version (as shown in *Help > About*): 4.35
* ...Anything else that can be useful...

## Community

- [X] I understand reporting an issue to this OSS project does not mandate anyone to fix it. Other contributors may consider the issue, or not, at their own convenience. The most efficient way to get it fixed is that I fix it myself and contribute it back as a good quality patch to the project.