fix(macOS): caculation for work area

[oscartbeaumont]

This PR rolls back one of the changes introduced in #13309 that offsets the work area by the visible frame reported by macOS.

I have noticed that on my primary monitor (whether that be internal or external to my laptop) that the visible frame reported by macOS is (0, 83). This causes the Tauri calculation to report the start position of the work area as being y 83 when it should be 0. If I use the changes in this PR I instead get 0 which points to the position directly under the macOS top bar as I would have expected.

I have left the x offset as it accounts for the size of the dock when it's on the left or the right.

Demo

We use the work area to caculate where to put the window when docking.

Before

On my primary monitor the work_area would report incorrect so the window would get position lower than expected. This would only happen on my primary monitor. It would work correctly on any secondary monitors.

Screen.Recording.2025-05-09.at.8.44.56.am.mov

After

Screen.Recording.2025-05-09.at.8.45.44.am.mov

Screen.Recording.2025-05-09.at.8.46.31.am.mov

[github-actions]

Package Changes Through e86b770

There are 7 changes which include tauri-bundler with patch, tauri with minor, @tauri-apps/api with minor, tauri-cli with patch, @tauri-apps/cli with patch, tauri-runtime-wry with patch, tauri-utils with minor

Planned Package Versions

The following package releases are the planned based on the context of changes in this pull request.

package	current	next
@tauri-apps/api	2.5.0	2.6.0
tauri-utils	2.4.0	2.5.0
tauri-bundler	2.4.0	2.4.1
tauri-runtime	2.6.0	2.6.1
tauri-runtime-wry	2.6.0	2.6.1
tauri-codegen	2.2.0	2.2.1
tauri-macros	2.2.0	2.2.1
tauri-plugin	2.2.0	2.2.1
tauri-build	2.2.0	2.2.1
tauri	2.5.1	2.6.0
@tauri-apps/cli	2.5.0	2.5.1
tauri-cli	2.5.0	2.5.1

Add another change file through the GitHub UI by following this link.

---

Read about change files or the docs at github.com/jbolda/covector