[Win32] Drag and drop offset on secondary monitor without monitor-specific scaling #2394

Describe the bug
When dragging and dropping elements on a secondary monitor when monitor-specific scaling is disabled, there is an offset between the actual and calculated drop position.
This is a result of a previous fix for the same when monitor-specific scaling was enabled, which did not consider the case when monitor-specific scaling is disabled:

• [win32] Ensure correct DPI awareness for DnD #2261

To Reproduce

• Start an Eclipse SDK with monitor-specific scaling disabled.
• Move the window to a secondary monitor that has a different zoom than the primary monitor
• Open, e.g., the project or package explorer and ensure that it contains some elements
• Drag and move an element inside that explorer

Expected behavior
Actual and calculated drop position should be the same on secondary monitors.

Screenshots
This is how it looks on 125% secondary monitor (with 100% primary monitor zoom):

Environment:

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

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

Version since
I20250707-1800