[Win32] Retrieving handle for cursor leads to non-disposed resource error #2355

Describe the bug
When retrieving a handle for a cursor that does not yet exist (because it is required for a different zoom), a non-disposed resource error is printed in case the non-disposed resource tracker is enabled.

This is caused by the Cursor#win32_getHandle() method creating a cursor instance just to extract the handle out of it. So it's actually intended that the cursor is not disposed, as that would also dispose the handle, but the implementation itself is strange as it should not be necessary to create such a dummy cursor at all:

When taking a look at the issue, it should also be considered that for the hotspotX/hotspotY values no scaling is considered, i.e., for every zoomed version of the cursor the same hotspot coordinates are used even though the image data is at different scales. That seems to be wrong.

To Reproduce
The error can be produced with the following simple snippet executed on a Windows machine with a primary monitor zoom <= 150%:

	Cursor cursor = new Cursor(Display.getDefault(), new ImageData(1, 1, 24, new PaletteData(0xFF, 0xFF00, 0xFF0000)), 0, 0);
	Cursor.win32_getHandle(cursor, 200);
	System.gc();
	Thread.sleep(1000);

Note that the System.gc() call is just there to ensure that the dummy cursor is cleaned up by GC, which yields the error, and the Thread.sleep() ensures that the JVM has sufficient time to print the error (as otherwise it may stop before the printing is finished).

Expected behavior
No non-disposed resource should be created and tracked when retrieving cursor handles. Actually I would not expect a dummy cursor to be created just for the sake of getting a handle at all.

Environment:

1. Select the platform(s) on which the behavior is seen:

• • All OS
• • Windows
• • Linux
• • macOS

2. Additional OS info (e.g. OS version, Linux Desktop, etc)
   Any Windows version

3. JRE/JDK version
   irrelevant

Version since
Eclipse 2024-12, precisely #1603

Workaround (or) Additional context
The error can just be ignored, there is no negative effect. It's just an irrelevant error that indicates a design flaw.