Save logical position when restoring on macos

[clouds56]

On macOS, it behaves strange with multiple monitor physical location. That is to say

Consider we have 2 monitor main and extra which physical size is 2560x1440 (scale: 2.0) and 1920x1080 (scale: 1.0)

+-----------+---------+
|     .<-A  |  .<-B   |
|   main    |  extra  |
| 2560x1440 |1920x1080|
|           |---------+
+-----------+

The physical position of A is (1200, 100), and the logical position of it would be (600, 50) due to scale factor.
The code before this PR would save (1200, 100) to "window-state.json" and everything just works.

But for point B, which "relative" physical position is (100, 100) (offset from left-top of "extra" monitor),
In this case, winit would tell the physical position is (1380, 100), which is the same as logical position (1380, 100).
If we save (1380, 100) to state file, and when restore, the winit would think we are at main screen and position to (640, 50) in logical position.

Point name	p1 = window.outer_position()	p2 = p1.to_logical(window.scale_factor())	restored p1 (in logical)	restore p2
A	PhysicalPosition(1200, 100)	LogicalPosition (600, 50)	LogicalPosition (600, 50)	LogicalPosition (600, 50)
B	PhysicalPosition(1380, 100)	LogicalPosition (1380, 100)	LogicalPosition (640, 50)	LogicalPosition (1380, 100)

TL;DR, in macOS the position system is consist in "logical" coordinates.

Edit:
This seems only macOS related, so I restrict patch only on cfg!(target_os = "macos")

There're several related issues you could reference

• [macOS] outer_position and set_outer_position may work unexpectedly with multiple monitors in different DPI tauri-apps/tao#816
• MonitorHandle::position and MonitorHandle::size metrics are unclear  rust-windowing/winit#2645
• [window-state] Maybe the restore_state API should use LogicalSize (not PhysicalSize) when restoring the window size tauri-apps/plugins-workspace#2620

[clouds56]

I found let adjustment = 56 failed on extra monitor.

Update:
It should be LogicalSize(0, 28) empirical.
(though I cannot find any documentation, the original code introduced in e923c64, could @jkelleyrtp kindly explain why it used to be 56 here?)

Tested on my macOS (15.4.1) and windows (11 24H2)

[clouds56]

What's blocking here?